[Helm/Release] [Helm/V3] Add initial support for OCI registries

[viveklak]

Proposed changes

This change adds OCI registry support:

1. Upgrades helm go module dependency to 3.8.0
2. Updates helm invokes codepath to initialize the registry client where necessary
3. Updates the helm release code to initialize the registry client
4. Works around a bug in v3.8.0 of Helm where a custom registry config is not honored.
5. Bump the integration test environment to use v3.8.0 of Helm CLI

This still needs some OCI specific integration test. This is a little more complicated since we need to provision an OCI registry first.

I followed the following for manually testing this:

1. Provision a Google artifact registry:

import * as gcp from "@pulumi/gcp";

registry = new gcp.artifactregistry.Repository("container-registry", {
    location: "us-central1",
    repositoryId: "oci",
    description: "example docker repository",
    format: "DOCKER",
});

2. gcloud auth configure-docker us-central1-docker.pkg.dev
3. Push a helm chart to the registry, e.g.:
   helm push nginx-6.0.5.tgz oci://us-central1-docker.pkg.dev/pulumi-development/oci
4. Use a pulumi program with a release set to track an OCI chart, e.g.:

nginxOci, err := helm.NewRelease(ctx, "nginx-oci", &helm.ReleaseArgs{
			Chart:     pulumi.String(`oci://us-central1-docker.pkg.dev/pulumi-development/oci/nginx`),
			Version:   pulumi.String("6.0.5"),
			Namespace: ns.Metadata.Name(),
			Values:    pulumi.Map{"service": pulumi.StringMap{"type": pulumi.String("ClusterIP")}},
		})

Related issues (optional)

Fixes #1477

[github-actions]

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

[github-actions]

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

[lblackstone]

Outside the scope of this PR, but we should probably expose this as an option for users

[made2591]

I'm looking forward to see this PR closed! 💪💪💪 keep rocking

[github-actions]

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

[SharpEdgeMarshall]

@viveklak we tried this new support for OCI registries but we were unable to dynamically pass the authentication (username, password).
After some digging looks like that your PR require you to login manually because helm sdk supports only the credentials from a config file, am I wrong?
If that's the case I think this approach is not suited for pulumi, can we do something with the component to authenticate on the fly to the registry? (like generate a helm config file on the fly)