[Fargate] [enhancement request]: elevated privileges for executing reliability tests

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

The community needs to be able to exercise reliability tests within serverless environments. Many members of the community already use external tools for that and those tools need to be granted permissions to run the tests intended to simulate the failures critical to their businesses.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Trying to orchestrate and simulate faults and failures of my services and their underlying infrastructure which use containers running in Fargate.

**Are you currently working around this issue?**
Currently unable to do this effectively and thus carrying additional risk and concern for the stability and reliability of the environment, which prevents confidence in running workloads.

**Additional context**
Here are the requirements

network,
file,
umount,
mount,

/entrypoint.sh rix,
/var/lib/gremlin/** rwix,
/var/log/gremlin/** rwix,
/etc/gremlin/** rwix,

# /dev/null
/dev rix,
/dev/null rwlix,

# Container runtime
/run/docker/runtime-runc/moby rwix,
/var/run/docker.sock rwix,
/run/crio/crio.sock rwix,
/run/runc rwix,
/run/containers/containers.sock rwix,
/run/containerd/runc/k8s.io rwix,

# We need access to Pid 1's real pid to resolve the container driver
# we're just taking a read perm here to accomplish this
file r @{PROC}/1/ns/pid,
ptrace read,

# fault injection capabilities
/proc/sysrq-trigger w,
/sys/fs/cgroup/** rw,
/proc/** rl,
# In order to join target container network space
/proc/[0-9]+/ns/net w,
# In order to assume the root of the target container
pivot_root,

# Needed for simulating faults
capability sys_boot,
capability sys_time,
capability sys_admin, # needed for setns
capability net_admin,
capability kill,
capability setfcap,
capability audit_write,
capability mknod,
capability net_bind_service,
capability setuid,
capability setgid,
capability chown,

# Needed for discovering services
capability dac_read_search,
capability sys_ptrace,

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

The issue names no repository files, tests, or entry points. Start by checking whether Fargate supports the requested network, mount, runtime-socket, ptrace, capability, and namespace permissions; define a concrete supported scope and acceptance criteria before implementation.

Written by the indexing model from the issue text.