[EKS] [Fargate] [request]: Update ulimits using annotations

### 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?
Implement an annotation to update ulimits (especially processes limit) of EKS on Fargate.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We have a jenkins that uses the kubernetes plugin to spawn new jobs as pods on EKS on Fargate.
I have a maven build job that hits the rlimit (processes limit) in EKS on Fargate and therefore throws an error:
```
[INFO] java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
```

**Are you currently working around this issue?**
As a workaround I will use ECS on Fargate

**Additional context**
I am aware that Kubernetes currently does not support rlimits:
https://github.com/kubernetes/kubernetes/issues/3595
However this only means that EKS itself is enforcing some hardcoded limit, since it does neither come from Kubernetes nor from Fargate.

The request targets EKS on Fargate and an annotation for changing ulimits; no repository files, tests, or implementation entry points are identified. Start by reviewing Kubernetes issue #3595 and the stated EKS/Fargate limits, then define the supported annotation behavior and validation. Done means the process limit can be raised for the described Jenkins/Maven pod.

Written by the indexing model from the issue text.