feat: add missing fields to --json output for snyk test and snyk sbom test

[paulrosca-snyk]

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?

Updates cli-extension-os-flows to the latest version.

Where should the reviewer start?

How should this be manually tested?

Running snyk test --json or snyk sbom test --json should now give a more comprehensive result, including some fields which were previously missing from the output.

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

The --json output of snyk test and snyk sbom test should now contain some fields which were previously missing i.e isDisputed, proprietary, severityBasedOn, alternativeIds and mavenModuleName (when applicable).

Risk assessment (Low | Medium | High)?

Low: This is an additive change and only affects the customers which use the new testing stack (e.g using --reachability or --risk-score-threshold).