[Fargate] [request]: Support for insecure registry

### 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**
Possibility to use a "insecure" Docker private registry (e.g. with self-signed certificate) for pulling Docker images.

**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?**
Currently, if the private registry has a self-signed certificate, we get an error from Fargate when we start the task:
CannotPullContainerError: Error response from daemon: Get https://my.private.registry/v2/: x509: certificate signed by unknown authority

**Are you currently working around this issue?**
There are actually two possible workarounds:
- Use ECS with EC2 instead of Fargate and customize the daemon.json with
```json
{
"insecure-registries" : ["my.private.registry:443"]
}
```

- Use ECR repository for my docker image, but it implies to pull image from my private registry and push them into ECR during the deployment pipeline.

No repository file, test, or entry point is identified. Start by reviewing the Fargate request and the reported x509 error, then compare the ECS with EC2 and ECR workarounds. Done means the requested support for pulling Docker images from a private registry with a self-signed certificate has an accepted implementation or decision.

Written by the indexing model from the issue text.