XRAY-157755 - Fix insecure tls flag traversal for maven projects

[gauriy-tech]

What & why

curation-audit/audit spawn a real mvn subprocess to build the dependency tree. Two bugs made
this fail silently for customers behind a TLS-intercepting proxy:

• --insecure-tls never reached that subprocess — DepTreeParams had no field for it.
• The real Maven error was swallowed behind log.Verbose (above DEBUG); only exit status 1 ever surfaced.

Changes

• Thread InsecureTls through DepTreeParams → MavenDepTreeManager → the spawned mvn command.
• Append both Wagon and native-resolver TLS-bypass properties (-Dmaven.wagon.http.ssl.* and
  -Daether.connector.https.securityMode=insecure), since Maven 3.9+ ignores the former.
• Embed captured Maven output in the returned error, bounded to 8KB, rune-boundary-safe.

Testing

New unit tests, offline via a fake mvnw script (see mvn_test.go). Also verified end-to-end
against a real Artifactory instance with curation-audit — no regressions.

Related: XRAY-157755

---

• 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.