Move reports to bazel-testlogs instead of bazel-bin

[furtib]

Describe the task

Move reports, created by our ruleset, to bazel-testlogs instead of bazel-bin.

Scope

What are reports?
Are they the plist files generated by CodeChecker?
Or are they the file/output generated with CodeChecker parse?

Definition of Done

Moved reports to bazel-testlogs instead of bazel-bin.

[Szelethus]

Lets discuss some motivation:

• The issue is not just that the analysis results are in one directory or another. Might not be nice, but its a minor annoyance.
• The real issue is, as far as I understand from the original reporter, that after bazel clean, the results (or at the very least, codechecker.log) are wiped and not reproduced from the remote cache after the fact.
• The reporter currently uses --remote_download_all to circumvent this.

[nettle]

Note that CodeChecker analyze is executed at bazel build phase, not test/run phase.
And all artifacts are not test artifacts but build artifacts, so I'm not sure it is possible at all.

[furtib]

I think users want to interface with the parse results, not the plist files.
So it would be more correct to place the results.txt (normal parse) and html parse artifacts into this directory.