[service] [request]: ECS Console Integration for FireLens CloudWatch Logs

### 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**
I propose enhancing ECS Console to seamlessly integrate and display logs from containers using FireLens with CloudWatch. This improvement would offer users a unified view of all container logs within the ECS Console.

**Which service(s) is this request for?**
This could be Fargate, ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I’m reaching out to request an enhancement for the AWS ECS console. Currently, when using the FireLens log driver to ship logs to CloudWatch, ECS Console fails to recognize and display logs not shipped by the awslogs driver. Despite successful CloudWatch integration, ECS Console only lists awslogs side-car logs and displays a “No log configurations for awslogs log driver” message for FireLens.
**Are you currently working around this issue?**
How are you currently solving this problem?

**Additional context**
Anything else we should know?

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

Start by reviewing the ECS Console, FireLens, CloudWatch, Fargate, and ECS behavior described in the request, especially the contrast with the awslogs driver. Determine whether the AWS console can recognize and display FireLens-shipped logs; done means container logs appear in the ECS Console with a unified view instead of the current no-log-configuration message.

Written by the indexing model from the issue text.