feat: add os dragonfly rollout release flag in ff interceptor

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

Adds the rollout-dfly-os-cli release flag to the cliv2 feature flag interceptor.

Where should the reviewer start?

How should this be manually tested?

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

N/A

[j-luong]

nitpick: maybe we can apply the rule of three here and refactor this?

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Path Synchronization Risk 🟡 [minor] The GetHandler function and the requestCondition regex are not perfectly synchronized. The regex in NewLegacyFeatureFlagInterceptor allows for an optional trailing slash, but the featureFlagPaths map keys are exact matches without trailing slashes. Additionally, the regex matches any path containing /cli-config/feature-flags/, whereas the map requires a /v1/ prefix. Consequently, requests that match the regex but differ in prefix or trailing slash will bypass the interceptor and fall back to the network. While this behavior is inherited from the previous implementation, the refactor to a map-based lookup is an opportunity to improve robustness by normalizing the path (e.g., trimming slashes) or ensuring the regex and map keys use a consistent base path. configKey, ok := featureFlagPaths[req.URL.Path] if !ok {

📚 Repository Context Analyzed This review considered 4 relevant code sections from 4 files (average relevance: 0.97) cliv2/internal/proxy/interceptor/legacyfeatureflaginterceptor.go (lines 1-81) cliv2/internal/proxy/interceptor/networkinjector.go (lines 1-44) cliv2/internal/proxy/interceptor/v1_analytics.go (lines 1-170) CONTRIBUTING.md (lines 301-400)