[EKS] [request]: EFS CSI driver should use service account role for IAM authorization

### 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**
When using the CSI driver to mount an EFS File System or Access Point, it should use the pod's service account IAM role for EFS authorization.

**Which service(s) is this request for?**
EKS, Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I want to use IAM to control what users and applications can access a specific file system or access point, and ensure that the IAM role for my particular pod is used for that authorization.

**Are you currently working around this issue?**

**Additional context**

**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 issue names no repository files, tests, or implementation entry points. Start by locating the EFS CSI driver integration and its EKS/Fargate IAM authorization path, then confirm how the pod service account role should be selected and what authorization behavior must be demonstrated before considering the request complete.

Written by the indexing model from the issue text.