feat: [AG-322] Add Studio Integration Name

[dan-arpino]

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?

Adding STUDIO as a Tracked Integration

Where should the reviewer start?

Only change is to sources.ts

How should this be manually tested?

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

No Update Needed

Risk assessment (Low | Medium | High)?

Low

Any background context you want to provide?

STUDIO integration is used for Snyk Studio background Secure At Inception Hooks

What are the relevant tickets?

AG-322

[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
⚠️	You've modified files in src/ directory, but haven't updated anything in test folder. Is there something that could be tested?

Generated by 🚫 dangerJS against 07c4112

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Tests 🟡 [minor] The PR adds a new integration name 'STUDIO' to the 'TrackedIntegration' enum but does not include any accompanying tests. According to the project's 'AGENTS.md' and 'dangerfile.js', modifications to the 'src/' directory should be accompanied by corresponding test changes in 'test/'. A test case should be added to ensure 'getIntegrationName' correctly parses 'STUDIO' from environment variables or flags. STUDIO = 'STUDIO',

📚 Repository Context Analyzed This review considered 4 relevant code sections from 3 files (average relevance: 0.59) CONTRIBUTING.md (2 segments, lines 231-413) dangerfile.js (lines 1-111) src/lib/analytics/sources.ts (lines 1-189)

🤖 Repository instructions applied (from AGENTS.md)

[danskmt]

Please double check if this change is really required: do we need this in analytics v1?
Also, maybe you want to use chore instead of feat in the commit message