Remote logging provider support for separate reader and (multiple) writer(s)

### Description The newly introduced `RemoteLogIO`, moves the abstraction for remote logging from the `logging.Handler` to purely `read` and `upload`, let's use this ticket to formalize the interface for remote logging solutions in Airflow 3.x. ### Use case/motivation Most handlers provided by providers implement `logging.Handler` have adopted this pattern. Our use-case is to ship logs to Kafka and read from ElasticSearch. We need to separate the reading and writing in order to keep control over the ingestion speed in a multi-tenant ES cluster. ### Related issues _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)