Upgrade EKS clusters' vpc-cni addons to be consistently of a new version

[consideRatio]

The aws-cni has been held back by eksctl by mistake upstream to a very old version, but via upstream work its now something that can upgrade to a newer aws-cni version using a modern eksctl version. Lets upgrade our clusters to the new version. Having it upgraded is something that could potentially be relevant for network policy enforcement, as the aws-cni v1.14+ is meant to be able to do that.

Steps

I think performing an upgrade command as described in https://infrastructure.2i2c.org/howto/upgrade-cluster/aws/#upgrade-eks-add-ons for each cluster is the single thing required, followed by verifying it updates and doesn't crash things.

Current aws-cni versions

A table below was generated by manually tweaking result of:

deployer config get-clusters --provider=aws | xargs -I {} deployer use-cluster-credentials {} "kubectl get ds -n kube-system aws-node -o yaml | grep amazonaws.com/amazon-k8s-cni:"

AWS Cluster	aws-cni version
2i2c-aws-us	v1.12.6
catalystproject-africa	v1.12.6
earthscope	v1.16.0-eksbuild.1
gridsst	v1.12.6
jupyter-health	v1.16.0-eksbuild.1
jupyter-meets-the-earth	v1.12.6
kitware	v1.16.0-eksbuild.1
nasa-cryo	v1.12.6
nasa-esdis	v1.12.6
nasa-ghg-hub	v1.12.6-eksbuild.2
nasa-veda	v1.12.6
openscapeshub	v1.12.6
opensci	v1.12.6
projectpythia	v1.16.0-eksbuild.1
smithsonian	v1.12.6
ubc-eoas	v1.12.6
victor	v1.12.6

Definition of done

All the following are upgraded and verified to be upgraded

• 2i2c-aws-us
• catalystproject-africa
• earthscope
• gridsst
• jupyter-health
• jupyter-meets-the-earth
• kitware
• nasa-cryo
• nasa-esdis
• nasa-ghg-hub
• nasa-veda
• openscapeshub
• opensci
• projectpythia
• smithsonian
• ubc-eoas
• victor