[EKS][Fargate] [request]: Support SYS_PTRACE 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 SYS_PTRACE for EKS Fargate ( already supported on ECS )

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Debugability and introspection of running workloads. May also allow for an alternative method for capturing process stdout to allow [sidecar logging with EKS Fargate](https://aws.amazon.com/blogs/containers/how-to-capture-application-logs-when-using-amazon-eks-on-aws-fargate/) in a more transparent method through stdout redirection.

See https://github.com/aws/containers-roadmap/issues/409 for the same request on ECS.

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

**Additional context**

**Attachments**

The issue names no repository files, tests, or implementation entry points. Start by reviewing the EKS Fargate request and the linked ECS issue to understand the requested SYS_PTRACE capability and current platform constraints. Done means SYS_PTRACE is supported for workloads running on EKS Fargate.

Written by the indexing model from the issue text.