feat: Upgrade Helm to v3 and AWS provider to v6

[dennisameling]

What does this PR do?

This upgrades the Helm provider to v3 and the AWS provider to v6.

Motivation

• Resolves Upgrade Helm provider to v3 #41

Test Results

I ran terraform init and terraform plan in the tests directory, which are passing correctly. I didn't go as far as to actually deploy the resources.

Additional Notes

[tb102122]

any news on a possible review date?

[KrawczowaKris]

could someone please take a look at this PR?

[dennisameling]

I don't think this repo is actively being monitored by anyone now that Bryant Briggs has left AWS. @novekm sorry for the ping - could you perhaps help us find the right people in AWS to get this reviewed? Thanks! 🙏🏼

[bryantbiggs]

I've reached out to some contacts at AWS to see what can be done about maintaining the projects (external maintainers is not typically possible).

However, in the interim I have forked the project and published two new releases:

• v1.2.0 if you want to stay on the prior version but avoid the version issues. This simply pins the provider versions to avoid errors - very similar to fix: A bug fix to pin the helm provider version to ~> 2.9 as there are breaking changes in 3.0.0 #38
• v2.0.0 which contains a number of improvements and corrections. You can see more details here

If we find a path for external maintainers then we can sync these changes back to this project and stop using the forked version. Until then, there is at least a path forward.

If you are using https://github.com/aws-blueprints/terraform-aws-eks-blueprints-addons I have started to do the same but have not made any enhancements other than forking and publishing a version with a pinned version to avoid errors. TBD on what changes will be made for that project