Describe the bug
When running insider in docker, the report gets generated in /opt/insider. This is a problem because the report is hard to access once the container has stopped. The image is basically mixing binaries and data. The report should written to a separate directory, for instance /var/insider so one may bind that to another volume, or sent to stdout.

To Reproduce
Steps to reproduce the behavior:

1. docker run --name container -v /path:/target insidersec/insider -tech csharp -target /target
2. docker comit container image
3. docker run -ti --entrypoint=sh image
4. ls -l /opt/insider

total 7032
-rwxr-xr-x    1 root     root       7012352 Jan 26 14:26 insider
-rw-r--r--    1 root     root         12505 May 26 09:03 report.html
-rw-r--r--    1 root     root          7443 May 26 09:03 report.json
-rw-r--r--    1 root     root        160403 May 26 09:03 style.css

Expected behavior
report placed somewhere else or output to stdout

Desktop (please complete the following information):

• OS: Windows
• Version docker latest

docker run insidersec/insider -version
Version: dev
Git commit:
Build date:
OS/Arch: linux/amd64