test: pull in cli-extension-os-flows PR with batched Feature Flag fetches

[bsalomon-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)
• [N/A] Highlights breaking API changes (if applicable)
• [N/A] Links to automated tests covering new functionality
• [N/A] Includes manual testing instructions (if necessary)
• [N/A] Updates relevant GitBook documentation (PR link: ___)
• [N/A] Includes product update to be announced in the next stable release notes

What does this PR do?

Pull in cli-extension-os-flows PR with batched Feature Flag fetches

• this is to trigger user journey tests

• Risk level is low: this method of checking feature flags was already used for some FFs, but not all. Now it's on all "snyk test" and "snyk monitor"

Where should the reviewer start?

Verify the user journey tests succeed

How should this be manually tested?

Check the CI/CD tests. Manual testing was already done in pre-prod.

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

Risk assessment (Low | Medium | High)?

Low

What are the relevant tickets?

https://snyksec.atlassian.net/browse/DGP-1762

[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
⚠️	"test: pull in cli-extension-os-flows PR with batched Feature Flag fetches" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against 0d682fe