[EKS] [request]: efs-csi addon resource-requests seem large and difficult to tune

### 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**
The EFS-CSI addon supports specifying resource-requests and limits. However these apply to all three containers in the controller-pod - "efs-plugin", "csi-provisioner", and "liveness-probe". The default request is 200m CPU, which gets multiple by three which means the default behavior is for each controller-pod to request 60% of a core.

This service runs replicated by default, so the out-of-the-box resource-request for the controller is 1.2 cores. This seems pretty large?

I expect that the different containers within the pod have different resource-use characteristics and don't all need to be requesting 1/5th of a core each.

The up-stream helm-chart allows making specific resource-requests per container.

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

**Are you currently working around this issue?**
N/A

**Additional context**
N/A

**Attachments**

Start by reading the upstream Helm chart mentioned in the issue and compare its per-container resource-request settings with the EFS-CSI addon behavior. Done means the addon lets users tune requests separately for the efs-plugin, csi-provisioner, and liveness-probe containers rather than applying one value to all three.

Written by the indexing model from the issue text.