[EKS] [request]: Support FIPS 140-2 for EKS Fargate

### 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**
What do you want us to build? Support FIPS 140-2 Compliance for ECS Fargate

**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?**
There is a customer demands where using EKS Fargate with enabling FIPS 140-2 Compliance on GovCloud region together, like ECS Fargate supports : https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-fips-compliance.html. Currently only EKS with EC2 would support FIPS 140-2, and would be great if AWS GovCloud users have more options to choose for AWS managed container service

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

Start by reading the linked ECS Fargate FIPS 140-2 documentation and comparing it with the issue's stated EKS and GovCloud requirements. This is a roadmap request with no repository file, test, or entry point named; done would require AWS to define and announce FIPS 140-2 support for EKS Fargate.

Written by the indexing model from the issue text.