fix: [OSM-2662] maven dverbose show resolved deps versions only

[gemaxim]

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: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Follow-up from #5891: keep only the versions resolved by maven in the Dverbose algorithm.
Tests are reverted to the values before this PR: the dependency that actually gets resolved by maven (not considered, but omitted) is at version 1.0.3. Same thing for the length of the dependencies array.

Where should the reviewer start?

This is introduced: snyk/snyk-mvn-plugin#190, see tests.

How should this be manually tested?

snyk test/monitor -- -Dverbose or snyk sbom on the fixtures projects.

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

[test, monitor, sbom] Maven Dverbose algorithm adds only the dependencies resolved by maven in the dependency graph/sbom.

What are the relevant tickets?

https://snyksec.atlassian.net/browse/OSM-2668