[EKS] [request]: Align bound service account token extended token expiration with upstream kubernetes

### 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**
Bound service account token extended token expiration is 1 year on upstream kubernetes, AKS and GKE, while EKS is 90 days.
I think EKS should align extended token expiration with other kubernetes (i.e. 1 year).

**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?**
90 days is too short and some libraries we use don't have a fix yet. For example, fabric8io/kubernetes-client doesn't has a fix yet: https://github.com/fabric8io/kubernetes-client/issues/2271. Changing the library require a lot of code changes and testings.

**Are you currently working around this issue?**
Restart the problematic pods before 90 days...

Start by reviewing the EKS bound service account token expiration behavior and the upstream Kubernetes, AKS, and GKE comparison described in the issue. Check whether EKS documents a configuration or service-side limitation; done means determining whether the extended expiration can be aligned to one year and documenting the outcome or implementation path.

Written by the indexing model from the issue text.