fix: ensure --json-file-output does not write to stdout

[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?

Update the GAF dependency to introduce a fix related to the output_workflow behaviour. Previously, in certain cases, JSON output would get printed to stdout when only the --json-file-output parameter was used.

Where should the reviewer start?

• GAF changes

How should this be manually tested?

Compare the stdout output for the command snyk sbom --format cyclonedx1.6+json --json-file-output=sbom.json. Before this changes the content would also be printed on stdout.

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

Fixes a bug where the JSON file output would be printed on stdout.

[snyk-io]

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

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

	Warnings
⚠️	"fix: don't output JSON for other workflow data when JSON file output is set" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against 32f65f0