feat: Update AWS load balancer controller IAM policy to align with latest policy provided by the LBC project

[bryantbiggs]

What does this PR do?

• Update AWS load balancer controller IAM policy to align with latest policy provided by the LBC project
• Update AWS load balancer controller chart to latest version

Motivation

• Aligns the policy used here with the policy provided by the LBC project https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/install/iam_policy.json
• Resolves Unable to create AWS Load Balancer Controller IAM policy #189
• Resolves Support for non-implicit AddTags in Create* API calls #200

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I ran pre-commit run -a with this PR

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[askulkarni2]

Should we bump the the lbc version while we are at it?

[dwgillies-bluescape]

I don't think this will actually fix the problem flagged by the AWS automatic scanner.

• elasticloadbalancing:CreateLoadBalancer

can be performed on any resource.

• elasticloadbalancing:AddTags

can only be performed on a select set of resources. According to the email I got, it must be performable on any resource that CreateLoadBalancer can affect, to satisfy the scanner. If the CreateLoadBalancer and AddTags operation only happen to operate on the same resources, then thats good but they probably should match to avoid problems down the road if the scope of CreateLoadBalancer ever grows or the scope of AddTags ever shrinks. They should probably be merged into a single policy Statement for safety down the road.

[bryantbiggs]

The policy here matches the policy specified by the AWS load balancer controller project