[EMR on EKS] [request]: Support additional customization to create managed endpoint

### 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**
What do you want us to build?
We would like to see more customization added to the create-managed-endpoint AWS CLI. Currently, it offers only limited customization, and we need to support customisation of the ingress resource and security group created for the managed endpoint.
https://docs.aws.amazon.com/cli/latest/reference/emr-containers/create-managed-endpoint.html

**Which service(s) is this request for?**
EMR on EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are unable to customize the ingress configurations, such as adding custom annotations via the CLI command, and this requires manual changes to the resources. It falls outside the best practices, and we need an automated way to manage the configuration.

**Are you currently working around this issue?**
How are you currently solving this problem?
Manually add the required annotations to the ingress resource and rules to security groups.

Start with the linked AWS CLI create-managed-endpoint reference and the EMR on EKS managed endpoint behavior described in the issue. Determine the supported customization requirements for the ingress resource and its security group; done means these configurations can be managed through the CLI without manual resource or security-group changes.

Written by the indexing model from the issue text.