feat: update nuget plugin to handle NX build

[snyk-tim]

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?

Updates the snyk-nuget-plugin which stops misclassifying NX Build projects (project.json) as NuGet projects. When an invalid project.json is found it now throws a NotSupportedEcosystem error.

The cli has been updated to handle this new NotSupportedEcosystem error by skipping over the file and logging a debug message.

NX Build project files have been added to the fixtures to test both snyk test and snyk sbom commands through the integration tests.

How should this be manually tested?

You can see this failing running one of the following command with an old CLI build in the test/acceptance/workspaces/mono-repo-project-manifests-only folder.

snyk test --print-graph --json --all-projects --fail-fast

snyk sbom --format cyclonedx1.5+json --all-projects

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

Stops misclassifying NX Build project.json as a NuGet project.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.