EKS NodeGroup: ReadWriteMany support for EBS

### 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**
Dynamically provisioning persistent volume using EBS

**Which service(s) is this request for?**
This could be EKS nodegroup

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Not able to provision persistent volume with accessModes:- ReadWriteMany in Persistent volume Claim

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

**Additional context**
Not able to scale, Rollout restart of delete pod with accessModes:- ReadWriteOnce volume

**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 concerns EKS nodegroups, EBS-backed persistent volumes, and Kubernetes PersistentVolumeClaims, but names no repository file, entry point, or test. Start by determining how this repository tracks EKS storage behavior and clarify the expected ReadWriteMany and rollout behavior. Done should include agreed acceptance criteria and validation for the requested support.

Written by the indexing model from the issue text.