chore: replace orchestration APIs by test API for native code.test im…

[PeterSchafer]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• 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: ___)

What does this PR do?

The main change is an implementation detail for the experimental native snyk code test, which will be using different APIs in the background.
The effect is, that some of the integration tests using mock server don't work anymore and turned out to be duplicates of existing User Journey tests. The duplicates have been removed now. In addition some tests that were limited to the Typescript implementation now also run against the golang native implementation.

The Risk of the change is low, as this feature is still behind a feature flag.

Where should the reviewer start?

How should this be manually tested?

With an org that has consistent ignores enabled, run snyk code test -d and observe that the debug logs to contain network request to the tests endpoint.

...
2025-01-23T20:42:34Z main - > request [0x14000556640]: POST https://api.snyk.io/hidden/orgs/d29ef58f-6684-481d-aca4-b24b58821b85/tests?version=2024-12-21
...

[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.spec.ts
⚠️	"chore: replace orchestration APIs by test API for native code.test implementation" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against c2f5e33