[EKS] [request]: Enable EventRateLimit admission controller

### 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**
What do you want us to build?
Enabling EventRateLimit admission controller

**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?**
We have a cluster with multiple namspaces, each namespace containing multiple applications.
We would like to limit the number of calls to API server to prevent it to get flooded by event requests from one namespace.
For achieving than we need to enable the EventRateLimit admission controller.
[EventRateLimit](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#eventratelimit)

Currently EventRateLimit is not part of enabled admission controllers [EKS platform-versions](https://docs.aws.amazon.com/eks/latest/userguide/platform-versions.html)

**Are you currently working around this issue?**
How are you currently solving this problem? We have no work around for this issue

**Additional context**

**Attachments**

The issue names no repository files, tests, or implementation entry points. Start by reading the linked EventRateLimit admission-controller reference and the EKS platform-versions documentation, then determine whether EKS supports enabling it. Done means the controller is available and enabled for the relevant EKS configurations, with documented behavior and validation.

Written by the indexing model from the issue text.