[EKS] [Request]: Consistency between AWS api and recommended versions for CNI, DNS, Kube-proxy

### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

Keep the versions from the AWS describe-add-on api (used by default) versions consistent with what's recommended by AWS in the documentation:
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/eks/describe-addon-versions.html

https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html
https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
From an enterprise stand point, managing thousands of clusters with varying networking versions is an issue. There's not a consistency in what's set by default versus what we should be using as recommended.

For example on a 1.23 EKS cluster, we would provision with 1.10.4-eksbuild.1 CNI default but if we upgrade from EKS 1.22 to 1.23 then it would be using 1.12.2-eksbuild.1 according to the recommendation on the docs. The same goes for coredns and kubeproxy.

Ideally we would like this to match up as closely as possible.

**Are you currently working around this issue?**
There's no workaround, just kind of guessing which version we should be using default vs recommended.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start by comparing the AWS EKS describe-addon-versions API with the linked documentation for VPC CNI, kube-proxy, and CoreDNS. Map the default and recommended versions for the cited Kubernetes releases, then verify that the requested consistency is achieved across those add-ons.

Written by the indexing model from the issue text.