Pick correct diff baseline when multiple technologies share a path Summary

[attiasas]

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

---

fix(audit): pick correct diff baseline when multiple technologies share a path

Summary

In audit diff mode, baseline scan results were matched by relative path only. When two technologies scanned the same directory (same absolute path, empty relative key), the wrong baseline could be chosen depending on iteration order. Matching now also considers the current target’s technology (with legacy behavior preserved when technology is unset).

Changes

• Extend SearchTargetResultsByRelativePath to accept technology and filter candidates via targetMatchesTechnologyForDiffCompare (utils/results/common.go).
• Thread targetResult.Technology through audit diff comparison and JAS GetResultsToCompareByRelativePath (commands/audit/audit.go, jas/common.go).
• Tests: same-directory npm vs poetry disambiguation, reversed slice order, and NoTech baseline compatibility (utils/results/common_test.go, jas/common_test.go).

Notes

• When technology is NoTech, behavior matches the previous path-only matching.

[github-actions]

---

🐸 JFrog Frogbot