[Emr on EKS] [issue]: Shorten the generated Service Account name

### 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**
EMR on EKS generates service account names more than 64 char, which is actually enforced in kubectl official client sdk. Because of that one can't use EMR on EKS from kubernetes sdk and create an operator or any programatic approach of interaction.
There is an equivalent issue filed on Cilium too which is also using client-go https://github.com/cilium/cilium/blob/b9f72929d45ba5d410ae7181c9db6770da4948e3/go.mod#L112 and is limited with the same approach https://github.com/cilium/cilium/issues/16579

**Which service(s) is this request for?**
This could be EKS, EMR

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Since AWS team has already pushed the longer sa names in production, to make this change available to new operator they can take a configmap for configuration as an input and provide the flag there.

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

Start by reviewing the requested 64-character limit, the referenced Cilium issue, and how EMR on EKS currently generates service account names. Done means new service account names fit the limit and the proposed configuration mechanism is defined for new operators; no repository file or test is identified.

Written by the indexing model from the issue text.