[EKS] [Mountpoint for Amazon S3 CSI Driver] [request]: Add support for controller tolerations

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We use karpenter + tf MNG, we have a taint on the MNG that the controller doesn't tolerate and the addon rejects any additional properties there so we can't add tolerations

**Are you currently working around this issue?**
Run the tf apply twice or have to move to applying teh chart on our own

**Additional context**
```
❯ aws eks describe-addon-configuration \
--addon-name aws-mountpoint-s3-csi-driver \
--addon-version v2.0.0-eksbuild.1 \
--query 'configurationSchema' \
--output text | jq
{
"$schema": "https://json-schema.org/draft/2019-09/schema",
"additionalProperties": false,
"description": "Configurable parameters for Mountpoint for S3 CSI Driver",
"properties": {
"controller": {
"additionalProperties": false
...
```

**Attachments**

Start with the EKS addon configuration schema from the `aws eks describe-addon-configuration` command shown in the issue, focusing on the `controller` properties and their `additionalProperties` restriction. Done means the Mountpoint for Amazon S3 CSI Driver addon accepts controller tolerations and can deploy on the tainted managed node group; verify this through the addon configuration and Terraform apply path.

Written by the indexing model from the issue text.