[EKS] [request]: Expose component SLI metrics from v1.metrics.eks.amazonaws.com

### 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**
Expose [`/metrics/sli` endpoints](https://kubernetes.io/docs/reference/instrumentation/slis/) for kube-scheduler and kube-controller-manager.

i.e. to be able to access via `kubectl get --raw "/apis/metrics.eks.amazonaws.com/v1/ksh/container/metrics/sli"` the same as the current set of metrics.

**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?**
Ideally to have the same observability configuration as our self-hosted clusters which have these endpoints accessible for scraping.

**Are you currently working around this issue?**
Skipping the scraping of these metrics

Start by reviewing the existing metrics.eks.amazonaws.com API behavior and the Kubernetes /metrics/sli documentation linked in the issue. Compare the current metrics endpoints with the requested kube-scheduler and kube-controller-manager endpoints, then verify the result using the stated kubectl get --raw command. Done means both SLI endpoints are accessible for scraping through the EKS metrics API.

Written by the indexing model from the issue text.