feat: create package alias for helm and updated integration tests

[kumadee]

• 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 master branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....

---

1. Allows intercepting helm CLI calls to be intercepted by jfrog CLI.

   We use helm-maven-plugin in our builds, which under the hood executes
   helm dependency, helm package and helm push commands. Without this
   feature we only have a dirty workaround to create a shim which mimics
   package aliasing feature in order to capture helm chart in a build-info.
   This allows us to keep using helm-maven-plugin and indirectly invoke
   jf helm to record the build-info along with maven artifacts. Feature was originally requested as a jfrog support ticket 427008

2. updated integration test for jf helm package

   relates to jf helm package fails to collect build-info when Chart.yaml and packaged chart archive are in different directories. jfrog-cli-artifactory#501

[naveenku-jfrog]

Please fix the branch sync issue before merging.

[kumadee]

@naveenku-jfrog

• I will rebase the branch based on current master when I am at office today.
• What about documentation update at https://docs.jfrog.com/artifactory/docs/jfrog-cli-package-alias? I could not find where is it defined.
• The integration test would fail without merging the dependent PR 501 in jfrog-cli-artifactory. Could you please check that PR as well?

[naveenku-jfrog]

Yes, jfrog/jfrog-cli-artifactory#501 pR needs to be merged first, I have that also, can you please address the comments.