update vpc cni to v1.11.2

[orsenthil]

Issue

Description of changes

• Improvement - Update golang to Go 1.18 amazon-vpc-cni-k8s#1991 (@orsenthil)
• Improvement - Update CNI to version v0.8.1 amazon-vpc-cni-k8s#1996 (@orsenthil)
• Improvement - Update CNI Plugins to v1.1.1 amazon-vpc-cni-k8s#1997 (@orsenthil)

Checklist

• Added/modified documentation as required (such as the README.md for modified charts)
• Incremented the chart version in Chart.yaml for the modified chart(s)
• Manually tested. Describe what testing was done in the testing section below
• Make sure the title of the PR is a good description that can go into the release notes

Testing

1. Setup a cluster

eksctl create cluster --name senthil-$(date +%d%b)-c2 --version 1.22 --region us-west-2 --with-oidc --ssh-access --nodegroup-name standard-workers --node-type c5.xlarge --nodes 2 --nodes-min 1 --nodes-max 2

2. I had to attach AmazonEKS_CNI_Policy to NodeGroup IAM policy as it wasn't present.
3. Remove existing CNI

kubectl delete -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/release-1.10/config/master/aws-k8s-cni.yaml

4. Install CNI from charts

$ helm install aws-vpc-cni --namespace kube-system ./charts/aws-vpc-cni
NAME: aws-vpc-cni
LAST DEPLOYED: Fri Jun  3 18:11:45 2022
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
aws-vpc-cni has been installed or updated. To check the status of pods, run:

kubectl get pods --namespace kube-system -l "app.kubernetes.io/name=aws-node,app.kubernetes.io/instance=aws-vpc-cni"

5. Verify pods are running.

$ kubectl get pods --namespace kube-system -l "app.kubernetes.io/name=aws-node,app.kubernetes.io/instance=aws-vpc-cni" -w
NAME             READY   STATUS    RESTARTS        AGE
aws-node-fd66p   1/1     Running   4 (2m48s ago)   9m34s
aws-node-jtlsq   1/1     Running   4 (2m48s ago)   9m34s

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jayanthvn]

lgtm