feat(code): parse project-tags for code test --report

[apzuk3]

Enable the CLI to parse the --project-tags flag for snyk code test --report and pass the tags to the code-client package.

Changes:

• Import and reuse existing generateTags function from monitor command
• Add tags to reportOptions when calling analyzeFolders for file-based report flow
• Add unit tests to verify tags are correctly parsed and passed to code-client
• Add unit test to verify tags are undefined when flag is not provided

This implementation reuses the battle-tested generateTags function that already handles tag validation and parsing for monitor and IAC commands.

Resolves: COIN-1891

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?

Where should the reviewer start?

How should this be manually tested?

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

[github-actions]

	Warnings
⚠️	There are multiple commits on your branch, please squash them locally before merging!
⚠️	"Merge remote-tracking branch 'origin/main' into feat/parse-project-tags-for-code-report" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against 393029a