chore: enable secrets acceptance tests in prod [PS-588]

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

Where should the reviewer start?

How should this be manually tested?

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

Risk assessment (Low | Medium | High)?

• Low

Any background context you want to provide?

What are the relevant tickets?

• PS-588

Screenshots (if appropriate)

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

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Reduced Verification 🟡 [minor] The refactor of the 'SARIF output payload validation' test removes the validation loop for result suppressions metadata. Previously, the test verified that each suppression contained 'justification', 'kind', and 'status' keys. This check was deleted, meaning the test no longer ensures that ignored secrets are correctly enriched in the SARIF output as claimed by its title. foundMultipleLocations = true; } });

📚 Repository Context Analyzed This review considered 4 relevant code sections from 4 files (average relevance: 1.00) CONTRIBUTING.md (lines 1-218) package.json (lines 1-224) dangerfile.js (lines 1-111) package-lock.json (lines 6-275)