[EKS] [request]: Ability to configure pod-eviction-timeout

**Tell us about your request**
I would like to be able to make changes to configuration values for things like `kube-controller`. This enables a greater customisation of the cluster to specific, bespoke needs. It will also go a long way in making the cluster more resilient and self-healing.

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

At present, we have a cluster managed by EKS. The default `pod-eviction-timeout` is five minutes, meaning that we can derail an instance and the control plane won't reschedule for five minutes. Five minute outages for things like our payment systems is simply unacceptable - the cost impact would be severe. At present, to the best of my knowledge, the control plane is not configurable at all.

What we would like to be able to do is provide configuration parameters via the AWS API or within a Kubernetes resources like a `ConfigMap`. Either or would mean, when we bring up new EKS clusters, we can automate the configuration of values like `pod-eviction-timeout`.

**Are you currently working around this issue?**
No, to the best of my knowledge, it isn't something that EKS presently supports.

Start by reviewing the EKS control plane configuration around kube-controller and the pod-eviction-timeout setting. Compare the two requested entry points—an AWS API parameter and a Kubernetes ConfigMap—and define how the setting would be applied when creating new clusters. Done means customers can automate this configuration and control the timeout.

Written by the indexing model from the issue text.