[fargate] [logDriver]: support "none" as a log driver option

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

Add support for "none" as a log driver option in ecs fargate to disable Docker logging.

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

We noticed a considerable amount of our bill is gone for CloudWatch Logs and we have another way to monitor our application and the logs aren't that important at this point.
We would like to have the option to enable/disable Docker container logging for ECS fargate.

As stated in the [docker documentation](https://docs.docker.com/config/containers/logging/configure/), we can disable the logs by providing "none" as a log driver option. We want to have that option supported for ECS fargate.

**What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now?**

We want to optimize our aws bill by removing resources we don't need.
it is not possible because we don't have the option to disable the docker logging from ecs fargate log driver.

**Are you currently working around this issue?**
How are you currently solving this problem?

Right now, we are have the following solutions
1- Using awslog driver and paying a lot for CloudWarch for something we are not using.
From looking to our bill, Charges are incurred by ingestion and archive storage of Amazon CloudWatch Logs.
To reduce ingestion costs, stop ingestion of unnecessary logs. To reduce storage costs, change the retention period for your log groups.
We are trying to stop ingestion of unnecessary logs.

2- Not choosing anything for log driver:
This will send logs to the ecs fargate storage and eventually cause a disk full.

3- Sending logs to a volume

This would reduce the bill but it is additional work for something we don't use.

We want something like what you are offering with [ecs agent](https://github.com/aws/amazon-ecs-agent/issues/528)

The issue concerns ECS Fargate log-driver configuration and links Docker's logging documentation and ECS agent issue #528. Start by reviewing those references and the Fargate service context; the request is complete when Fargate supports the "none" log-driver option to disable container log ingestion.

Written by the indexing model from the issue text.