fix: support using sarif and json output files at the same time

[CatalinSnyk]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

This PR changes the behaviour of the golang native code test implementation to match the typescript implementation with regards to output file handling.

1. It enables to specify and write two different files when specifying --sarif-file-output and --json-file-output.
2. It mimics the behaviour where testing a code base without issues creates an empty sarif file for --sarif-file-output but doesn't create a file for --json-file-output.

Where should the reviewer start?

The main changes can be found in this GAF PR.
This PR also adds user journey tests for both cases and adapt the output configuration based on the new options.

How should this be manually tested?

Using --json-file-output and --sarif-file-output for code scans with CCI enabled should create two files like the parameters would specify. This can be compared to the old behaviour where only one file was being created.

What's the product update that needs to be communicated to CLI users?

1. It enables to specify and write two different files when specifying --sarif-file-output and --json-file-output.
2. It mimics the behaviour where testing a code base without issues creates an empty sarif file for --sarif-file-output but doesn't create a file for --json-file-output.

Risk assessment (Low | Medium | High)?

The Risk of the change is Low as it affects the rendering engine currently only used for CCI for which we have a good test coverage.

Ref: CLI-860
Ref: CLI-980

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[github-actions]

	Warnings
⚠️	Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones. A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax. Files found: test/jest/acceptance/snyk-code/snyk-code-user-journey.spec.ts

Generated by 🚫 dangerJS against 7f28efa