[EKS] [request]: Set resource limits for efs-csi pods so they have guaranteed resources

### 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**
Please add resources limits to the efs-csi EKS addon so that the pods will be guaranteed resources on the nodes. ebs-csi addon does this already.

```bash
» kubectl describe no | grep efs kube-system efs-csi-controller-57bc7b678f-8khw2 0 (0%) 0 (0%) 0 (0%) 0 (0%) kube-system efs-csi-node-vr6tp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
```

**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?**
Problem is that the efs-csi resources will not get guaranteed resources if other pods on the node want to use them.

**Are you currently working around this issue?**
No workaround, haven't implemented setting them post-install yet.

**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.)

The request concerns resource settings for the EKS efs-csi addon; start by comparing it with the ebs-csi addon, which already sets resources. Done means the efs-csi controller and node pods receive guaranteed resources on their nodes.

Written by the indexing model from the issue text.