[eks] [request]: Support specifying API Server Metric Cardinality Enforcement flag

### 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**

Let users configure this API Flag: https://github.com/kubernetes/enhancements/issues/2305

**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?**

API Server metrics are extremely high cardinality to begin with and only gets exponentially worse the more CRDs you install into the control plane. The upstream community has provided this flag as a source side control to this.

This is extremely problematic for many installations of Prometheus or managed prometheus providers where you are paying for every series generated, such as AWS Managed Prometheus or Grafana Cloud.

**Are you currently working around this issue?**

Attempting to write prometheus relabel rules to drop what we don't need.

Start by reading the linked Kubernetes enhancement issue 2305 and the EKS roadmap context to understand the API Server Metric Cardinality Enforcement flag. Done means EKS users can configure this flag and reduce unwanted API server metric series, with the supported configuration and limitations documented.

Written by the indexing model from the issue text.