JFrog Curation - Support "Implicit curation" - Run curation after "install" command failure

[asafambar]

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

---

[eyalbe4]

Does jfrog-cli-security include a mechanism to check whether the user has JFrog Curation enabled, and if so skip the execution for the "jf curation-audit" command?

answer:
yes

[eyalbe4]

This if statement that checks whether the error is nil or not should be placed inside the jfrog-cli-security module. This is to reduce the dependecy of jfrog-cli-security on this module, in case changes are needed to the curation logic.
The approach taken for "pip" is better, so let's adopt it here as well -

[asafambar]

its a bit more complicated for npm, I will check again