Add support for side-by-side installs of Helm v3 and v4

[burck1]

ref: helm/helm#31764

With the chocolatey kubernetes-helm package, there is currently no easy way to install v3 and v4 side-by-side on Windows. This is due to the Chocolatey standards for supporting side-by-side where the expectation is to "Create separate package IDs for each major version".

I added folders for new kubernetes-helm3 and kubernetes-helm4 packages and I updated the existing kubernetes-helm package to be a metapackage that depends on the kubernetes-helm4 package. For the update.ps1 scripts, I modified them to call the GitHub releases API rather than getting the HTML page so that the results can be filtered for v3 vs v4.

Note: I'm not really sure if the AU script will automatically register the new packages or if you will need to setup something on https://community.chocolatey.org first?

Let me know if you have any questions.

[burck1]

Hmm. I see this in the build output: https://ci.appveyor.com/project/synax/chocolatey-packages/builds/53551385

[4/6] kubernetes-helm ERROR:
Choco pack failed with exit code 1 (17.12s)
[5/6] kubernetes-helm3 ERROR:
Chocolatey v0.10.15 An ApiKey was not found for 'https://push.chocolatey.org'. You must either set an api key in the configuration or specify one with --api-key. (18.24s)
[6/6] kubernetes-helm4 ERROR:
Chocolatey v0.10.15 An ApiKey was not found for 'https://push.chocolatey.org'. You must either set an api key in the configuration or specify one with --api-key. (17.99s)

For the "... ApiKey was not found ..." error, I'm guessing that's because the new packages will need to be setup in some way on https://community.chocolatey.org/ first. Is that something you (maintainers) can setup?

For the "Choco pack failed with exit code 1" error, I'm not sure how to debug that error. If you have any ideas please let me know, or else I'll fiddle with it till I figure it out.