feat: add project tags for code test report flow

[apzuk3]

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

[snyk-io]

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

Status	Scan Engine	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
⚠️	Please make changes to snyk help text in Gitbook. Changes will be automatically synchronised to Snyk CLI as a scheduled PR. For more information, see: help/README.md.

Generated by 🚫 dangerJS against de9a766

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Layering Violation 🟡 [minor] The core library logic in analysis.ts (located in src/lib) now imports generateTags from the CLI command directory (src/cli/commands/monitor). This creates a dependency from the library layer onto the CLI layer, which is an architectural regression. This can lead to circular dependencies and issues when using Snyk as a programmatic library where CLI components may not be initialized or present. import { generateTags } from '../../../cli/commands/monitor';

📚 Repository Context Analyzed This review considered 10 relevant code sections from 7 files (average relevance: 0.53) package.json (lines 1-223) help/cli-commands/code.md (lines 1-14) package-lock.json (2 segments, lines 6-275) help/cli-commands/test.md (lines 34-195) src/lib/plugins/sast/analysis.ts (2 segments, lines 1-276) help/cli-commands/code-test.md (lines 1-145) src/lib/types.ts (2 segments, lines 1-294)

[PeterSchafer]

Issue: Please see this doc. The help contents is currently curated in gitbook and synchronized with the CLI automatically