Fix use wrapper mvn

[attiasas]

Fix using wrapper for Maven dependency tree

NewMavenDepTreeManager was constructing a new DepTreeParams with only Server and DepsRepo, silently dropping UseWrapper (and UseIncludedBuilds). This meant RunMvnCmd always executed mvn even when the project uses a Maven wrapper (./mvnw), causing failures on systems without a global Maven installation.

The fix passes the full params object to NewDepTreeManager so all fields are preserved.

Changes

• sca/bom/buildinfo/technologies/java/mvn.go: Pass the original params to NewDepTreeManager instead of constructing a partial copy with only Server and DepsRepo.
• sca/bom/buildinfo/technologies/java/mvn_test.go:
  • Add TestNewMavenDepTreeManagerPreservesAllParams — unit test verifying all DepTreeParams fields propagate correctly through the constructor.
  • Update TestMavenWrapperTrees to pass UseWrapper: true so it actually exercises the ./mvnw code path.
  • Update TestDepTreeWithDedicatedCache to pass UseWrapper: true since it also uses the wrapper test project.

---

• The pull request is targeting the dev branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....
• All static analysis checks passed.
• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• Updated the Contributing page / ReadMe page / CI Workflow files if needed.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

[github-actions]

---

🐸 JFrog Frogbot