Handle Fluent Bit logs like metrics with its own input plugin

Rather than simply directing Fluent Bit logs to a defined file. Why not adopt or offer the model that has been implemented for Fluent Bit Metrics. A simple plugin that can take the logs and associate them with a tag and therefore buffered as if they're an input stream. Then the user can direct the logs, so if all logs are being aggregated to OpenSearch then it becomes really simple to include Fluent Bit logs as well.

**Describe the solution you'd like**
Simple input plugin that treats Fluent Bit logs as a source - eliminating the I/OI overhead of tailing its own log file

**Describe alternatives you've considered**
Orivude an OOTB configuration for tailing own log files.

**Additional context**
Simplifies the operational setup for Fluent Bit. It could be argued that it is close to the 13 Factor app as the logic now has no interest in directing its logging (beyond just putting it in the hands of a input plugin)