Helm provider v3 upgrade: fix syntax for provider block

Bug

Description

Job broke due to unpinned upgrade from v2 to v3 of the Helm provider:

$ terraform init -input=false
Initializing the backend...
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
- ci in ../../main
Downloading registry.terraform.io/terraform-aws-modules/eks/aws 19.21.0 for ci.eks...
- ci.eks in .terraform/modules/ci.eks
- ci.eks.eks_managed_node_group in .terraform/modules/ci.eks/modules/eks-managed-node-group
- ci.eks.eks_managed_node_group.user_data in .terraform/modules/ci.eks/modules/_user_data
- ci.eks.fargate_profile in .terraform/modules/ci.eks/modules/fargate-profile
Downloading registry.terraform.io/terraform-aws-modules/kms/aws 2.1.0 for ci.eks.kms...
- ci.eks.kms in .terraform/modules/ci.eks.kms
- ci.eks.self_managed_node_group in .terraform/modules/ci.eks/modules/self-managed-node-group
- ci.eks.self_managed_node_group.user_data in .terraform/modules/ci.eks/modules/_user_data
Downloading registry.terraform.io/terraform-aws-modules/iam/aws 4.7.0 for ci.irsa-ebs-csi...
- ci.irsa-ebs-csi in .terraform/modules/ci.irsa-ebs-csi/modules/iam-assumable-role-with-oidc
Downloading registry.terraform.io/terraform-aws-modules/iam/aws 5.58.0 for ci.vpc_cni_irsa...
- ci.vpc_cni_irsa in .terraform/modules/ci.vpc_cni_irsa/modules/iam-role-for-service-accounts-eks
Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding latest version of hashicorp/helm...
- Finding hashicorp/kubernetes versions matching ">= 2.10.0"...
- Finding hashicorp/time versions matching ">= 0.9.0"...
- Finding hashicorp/tls versions matching ">= 3.0.0"...
- Finding hashicorp/cloudinit versions matching ">= 2.0.0"...
- Finding hashicorp/aws versions matching ">= 2.23.0, >= 4.0.0, >= 4.33.0, >= 4.57.0, 5.99.1"...
- Installing hashicorp/helm v3.0.1...
- Installed hashicorp/helm v3.0.1 (signed by HashiCorp)
- Installing hashicorp/kubernetes v2.37.1...
- Installed hashicorp/kubernetes v2.37.1 (signed by HashiCorp)
- Installing hashicorp/time v0.13.1...
- Installed hashicorp/time v0.13.1 (signed by HashiCorp)
- Installing hashicorp/tls v4.1.0...
- Installed hashicorp/tls v4.1.0 (signed by HashiCorp)
- Installing hashicorp/cloudinit v2.3.7...
- Installed hashicorp/cloudinit v2.3.7 (signed by HashiCorp)
- Installing hashicorp/aws v5.99.1...
- Installed hashicorp/aws v5.99.1 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
$ set -e # collapsed multi-line command
Workspace "maste-43623" doesn't exist.
You can create this workspace with the "new" subcommand 
or include the "-or-create" flag with the "select" subcommand.
$ terraform validate
╷
│ Error: Unsupported block type
│ 
│   on ../../main/main.tf line 18, in provider "helm":
│   18:   kubernetes {
│ 
│ Blocks of type "kubernetes" are not expected here. Did you mean to define
│ argument "kubernetes"? If so, use the equals sign to assign it a value.
╵

BigBang Version

3.0.0