Bump go-git to v5.13.1 (CVE-2025-21613)

[hightoxicity]

Bump go-git to v5.13.1 to avoid binary to be security scanned as unhealthy vs CVE-2025-21613

• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• 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 ./....

---

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[EyalDelarea]

Hey @hightoxicity,

Thanks for your contribution!

As highlighted in the following PR: #2816, this introduces a breaking change in our repositories, which needs to be resolved before we can proceed with updating the dependency.

[hightoxicity]

#2816

Hey @EyalDelarea does it only mean jfrog/froggit-go#142 need to be merged, version tagged there and froggit-go dependency updated with new version into jfrog-cli dependencies?

[EyalDelarea]

#2816

Hey @EyalDelarea does it only mean jfrog/froggit-go#142 need to be merged, version tagged there and froggit-go dependency updated with new version into jfrog-cli dependencies?

This issue needs to be addressed in Froggit-Go, as the update is introducing breaking changes to the APIs. Once fixed, it should be released and then updated across all the other relevant places.