[eks] [request]: Document/discuss how the upstream change to beta APIs will be handled by EKS

### 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**
As of Kubernetes v1.24 [KEP-3136](https://github.com/kubernetes/enhancements/pull/3137) has been approved and means that all new beta APIs will be off by default. AFAIK the current EKS behaviour mirrors upstream Kubernetes and has beta APIs enabled by default, with no user customisation. If this approach is continued for EKS v1.24 all new beta APIs will be off by default and the user will not be able to customise them.

I think there is probably some discussion to be had here. I'm not specifically asking for user customisation, although that would solve the problem if beta APIs could be toggled, I'd like beta APIs to be evaluated subjectively and as EKS tracks behind stable Kubernetes there is the benefit of hindsight to be had.

**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?**
Beta APIs can be useful and having them always off in EKS, which can trail significantly behind upstream, will stifle innovation and potentially cause significant issues.

**Are you currently working around this issue?**
n/a

**Additional context**
n/a

**Attachments**
n/a)

Start by reading Kubernetes KEP-3136 and the issue's description of EKS v1.24 beta API behavior. There are no files, tests, or entry points named. Done would be a documented, agreed approach for how EKS evaluates and handles upstream beta APIs, but the issue does not define that decision.

Written by the indexing model from the issue text.