Add risky tech callback guard after techs detection

[eranturgeman]

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

---

This PR adds ability to accept and execute a function that guards from executing risky technologies without proper validations.
When executing Frogbot we are exposed to untrusted code contributions (through PRs). In Maven and Gradle when we use the dep-tree plugins the tasks being executed are running scripts found in the repo prior to the task itself. In order to prevet malicious code execution we are adding an optional guard function that can be provided to audit. if not provided - no-op

[attiasas]

Nice, check out my comment

[attiasas]

LGTM

[github-actions]

---

🐸 JFrog Frogbot