fix(general): Improve error handling to surface the most relevant error

[PeterSchafer]

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?

Implements a first iteration error prioritization to ensure the most relevant/severe error is displayed and used for exit code derivation when multiple errors occur during CLI execution.

Changes:

• Added FindMostRelevantError() function that finds the most relevant error from a list based on:
• Updated error processing to use FindMostRelevantError() for selecting which error to display and derive exit codes from
• Moved and extended maintenance error tests to a dedicated test file

Where should the reviewer start?

1. Core logic for FindMostRelevantError() and priority comparison in the CLI errors package
2. Usage in the processError() function
3. Unit tests covering various scenarios

How should this be manually tested?

TEST_SNYK_COMMAND=binary-releases/snyk-macos-arm64 npx jest test/jest/acceptance/maintenance.spec.ts

[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 Test Coverage 🟡 [minor] The test case 'test a single file' in the Snyk Code user journey has been disabled using it.skip. While this might be intended to stabilize CI, it removes verification for a common user workflow (scanning a specific file) and should be addressed or documented as a known issue. it.skip('test a single file', async () => {

📚 Repository Context Analyzed This review considered 20 relevant code sections from 12 files (average relevance: 0.96) dangerfile.js (lines 1-111) CONTRIBUTING.md (lines 1-218) cliv2/cmd/cliv2/exitcode.go (lines 1-197) cliv2/cmd/cliv2/main.go (2 segments, lines 1-202) cliv2/internal/cliv2/cliv2.go (2 segments, lines 508-624) cliv2/cmd/cliv2/behavior/maperrortoexitcode.go (lines 1-29) src/cli/main.ts (lines 1-235) ... and 5 more file(s)

[github-actions]

	Warnings
⚠️	Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones. A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax. Files found: test/jest/acceptance/snyk-code/snyk-code-user-journey.spec.ts
⚠️	There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 30d60bf