[EKS] [request]: Allow Kubernetes Events TTL configuration

By default, k8s only keeps an hour worth of events. This TTL is configurable through the --event-ttl of kube-apiserver. Can we expose this configuration for EKS so people can keep more history for debug purpose?

### 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?

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

**Are you currently working around this issue?**
How are you currently solving this problem?

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Review the EKS request and the Kubernetes kube-apiserver --event-ttl setting described in the issue. Determine how this configuration could be exposed for EKS and define done as allowing customers to retain Kubernetes Events for a configurable period.

Written by the indexing model from the issue text.