[FireLens] [request]: FireLens/Fluent Bit as a unified observability solution

### 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**
At the moment, users often run 2 - 3 side cars or daemons for observability. Fluent Bit/FireLens takes care of logs, but then you need a metrics agent and a tracing agent. This proliferation of agents adds management overhead.

We are evaluating turning Fluent Bit into a more general observability solution. The community is already working on a [Statsd input support](https://github.com/fluent/fluent-bit/pull/1756).

This idea is very early-stage; please give us your thoughts and let us know if you think it would be valuable.

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

**Update: Please see the comments, plans have changed. AWS Distro for OT will be our unified router.**

Start by reading the six issue comments and the update stating that plans changed. The request is an early-stage proposal with no files, tests, or implementation entry point named; determine whether it is still applicable or has been superseded by AWS Distro for OT.

Written by the indexing model from the issue text.