feat: add acceptance tests to compare unified scanner flow with legac…

[tonidevine1]

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 acceptance tests to compare unified scanner flow with legacy flow for legacy package managers. This ensures that changing to the new flow is consistent for these legacy package managers.

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

Risk assessment (Low | Medium | High)?

Low

Any background context you want to provide?

n/a

What are the relevant tickets?

https://snyksec.atlassian.net/jira/software/c/projects/CMPA/boards/5466?assignee=60162bfac8c36c00698fa2d4&selectedIssue=CMPA-595

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.