[EKS] [request]: Bump default NFS version on EKS AMIs

### 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 ensure that the default NFS client version on EKS AMIs is 4.2 or later.

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

I need to use ACLs with an NFS volume. Unfortunately, Kubernetes does [not allow specifying mount arguments](https://github.com/kubernetes/kubernetes/issues/96284) on an NFS volume. As a result, all of my NFS volumes use the NFS version that is default on the AWS EKS AMI.

That is NFS v4.1 on the latest 1.19 EKS AMIs. There is a bug in NFS v4.1 that keeps ACLs from working properly: https://superuser.com/a/1605209

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

I am not, so features in my product are broken. I could rearchitect away from NFS volumes and use PVCs instead (which allow setting arguments, but create limitations around namespaces), or build my own AMIs. The other option is to monkey with the umask, which I would rather avoid for other reasons. Bumping the version of NFS would be awesome 😄

**Additional context**

**Attachments**

Start by locating the EKS AMI build or configuration that determines the default NFS client version; no repository file is named in the issue. Verify the current default is NFS 4.1 and test the requested 4.2-or-later default with NFS ACLs. Done means EKS AMIs use the newer default without requiring per-volume mount arguments.

Written by the indexing model from the issue text.