[Fargate] [bug/regression]: InitProcessEnabled not working anymore with 1.4.0?

### 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**
When I try to enable the `InitProcessEnabled` `LinuxParameter`:

```json
"LinuxParameters": {
"Capabilities": {},
"InitProcessEnabled": true
}
```

I get this error when trying to launch my task:

```
"reason": "CannotStartContainerError: ResourceInitializationError: failed to create new container runtime task: OCI runtime create failed: container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \"rootfs_linux.go:58:...",
```

**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?**
I'm trying to make use of the `docker run --init` feature to reap zombie processes that might be caused by my container (e.g. Chrome processes used for creating PDFs).

**Are you currently working around this issue?**
I currently have `InitProcessEnabled` set to `false`. This is fine for testing but will not work for production. If needed I will look into directly using tini (https://github.com/krallin/tini) in my container images.

Start by reproducing the Fargate task launch with the LinuxParameters.InitProcessEnabled setting shown in the issue and compare it with the reported OCI runtime error. Done means a task using InitProcessEnabled=true launches successfully and can reap child processes; the issue does not name project files or tests to inspect.

Written by the indexing model from the issue text.