Support Curation to run after package manager installation failure

[asafambar]

Support Curation to run after package manager installation failure

• 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.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

Description:
This PR introduces a wrapper for the curation command that handles failure errors from installation commands (such as go, mvn, pip, npm, etc.). If the error is deemed relevant to curation—specifically, a 403 error that might be due to curation—then the curation command will run on the project to provide the status of blocked packages.

Currently, the wrapper only supports cases where you have a valid curation entitlement on the JPD you are directly working with (smart to DMZ on other JPDs won't work). Additionally, it only runs during a GitHub Actions step, which requires a specific environment variable to be provided.

depends on:
jfrog/jfrog-cli-core#1225
jfrog/build-info-go#267
jfrog/jfrog-cli#2639

[attiasas]

Nice! please take a look at my comments.

• Please update PR description
• Please add integration tests for this new cmd in scan_test.go (not including adding unit tests)

[github-actions]

---

🐸 JFrog Frogbot