feat: create package alias for helm

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 support ticket 427008**

Author: kumadee

ghostfrog_test.go

@@ -468,10 +468,11 @@ func TestGhostFrogHighFanOutStress(t *testing.T) {
 // E2E-030: setup-jfrog-cli native integration
 func TestGhostFrogSetupJFrogCLINativeIntegration(t *testing.T) {
 	homeDir := initGhostFrogTest(t)
-	installAliases(t, "npm,mvn,go,pip")
+	tools := []string{"npm", "mvn", "go", "pip", "helm"}
+	installAliases(t, strings.Join(tools, ","))
 
 	binDir := aliasBinDir(homeDir)
-	for _, tool := range []string{"npm", "mvn", "go", "pip"} {
+	for _, tool := range tools {
 		_, err := os.Stat(aliasToolPath(homeDir, tool))
 		require.NoError(t, err, "alias for %s should exist", tool)
 	}
@@ -484,7 +485,7 @@ func TestGhostFrogSetupJFrogCLINativeIntegration(t *testing.T) {
 	// Verify alias dir is populated
 	entries, err := os.ReadDir(binDir)
 	require.NoError(t, err)
-	assert.GreaterOrEqual(t, len(entries), 4, "should have at least 4 alias entries")
+	assert.GreaterOrEqual(t, len(entries), len(tools), fmt.Sprintf("should have at least %d alias entries", len(tools)))
 }
 
 // E2E-031: Auto build-info publish (requires Artifactory)

packagealias/packagealias.go

@@ -33,6 +33,7 @@ var SupportedTools = []string{
 	"docker",
 	"gem",
 	"bundle",
+	"helm",
 }
 
 // AliasMode represents how a tool should be handled