[EKS][Fargate][request]: Increase number of vCPU in 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**
Increase the number of vCPU available in Fargate to at least 64.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are using Fargate for a computationally heavy application with unpredictable loads. Threading is important in order to get good performance. The 16 vCPU limit is making it hard for us to use Fargate for our use case.

**Are you currently working around this issue?**
We might need to look into setting up our own EC2 instances and handle scaling.

**Additional context**
When using 8 threads, we have observed that requesting 16 vCPU gives better performance. This might be related to the underlying EC2 instance, see [#2019](https://github.com/aws/containers-roadmap/issues/2019).

**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 with the request for at least 64 vCPUs in AWS Fargate for EKS and review the related issue #2019 for context about the observed performance. The request is complete when Fargate supports the higher vCPU capacity or the roadmap records a clear resolution; no repository files or tests are identified.

Written by the indexing model from the issue text.