[EKS] [request]: Allow user to modify the kube-apiserver flag --service-account-max-token-expiration

### 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**
I would like to make requests to TokenRequest API for tokens that have expiration > 24 hours. When I try to make a request to TokenRequest API for 30 day expiration, I receive a token that has 1 day expiration.

**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?**
This cluster is a development cluster, and I don't want users to have to fetch a new token every day in order to access this development cluster.

**Are you currently working around this issue?**
Yes, users have to refresh their token every day. But for kubernetes clusters with other cloud providers this is not a restriction, so other cloud provider kubernetes clusters have a better user experience.

The request concerns EKS and the Kubernetes TokenRequest API, specifically kube-apiserver's --service-account-max-token-expiration flag. No repository files or tests are identified; begin by locating the EKS control-plane configuration surface and reviewing the current 24-hour behavior. Done means users can request tokens longer than 24 hours, including a 30-day request, through a configurable maximum.

Written by the indexing model from the issue text.