Version skew of EKS managed node group should be updated

[xiangyanw]

Describe the problem

EKS has updated its version skew policy of managed node groups.
https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html

If the kubelet on your managed and Fargate nodes is on Kubernetes version 1.25 or newer, you can update your cluster up to three versions ahead without updating the kubelet version. For example, if the kubelet is on version 1.25, you can update your Amazon EKS cluster version from 1.25 to 1.26, to 1.27, and to 1.28 while the kubelet remains on version 1.25.

If the kubelet on your managed and Fargate nodes is on Kubernetes version 1.24 or older, it may only be up to two minor versions older than the kube-apiserver. In other words, if the kubelet is version 1.24 or older, you can only update your cluster up to two versions ahead. For example, if the kubelet is on version 1.21, you can update your Amazon EKS cluster version from 1.21 to 1.22, and to 1.23, but you will not be able to update the cluster to 1.24 while the kubelet remains on 1.21.

Below statement in aws-eks-best-practices/content/upgrades/index.md should be updated too:
EKS managed node groups and nodes created by EKS Fargate Profiles only support 1 minor version skew between the control plane and data plane.

References
https://aws.github.io/aws-eks-best-practices/upgrades/#upgrade-your-control-plane-and-data-plane-in-sequence