fix(Monitoring): Serializable log middleware

[frascuchon]

Also, review and format the class name

[davidberenstein1957]

@frascuchon I updated the logic for the default mapper

[davidberenstein1957]

maybe it makes sense to create a try-except for the records mapper that provides some information about the input-output and that the _records_mapper is causing the error and can be adapted manually.

[frascuchon]

+1

[frascuchon]

+1

[frascuchon]

Done @davidberenstein1957

Now, the middleware is using a BaseMonitor object, so the logic to send data to Argilla remains aligned with the rg.monitor behavior.

The code has changed a little bit. The main thing here is to provide the records properly in the _prepare_argilla_data method (old log_to_argilla).

Let me know if you have questions.

[frascuchon]

Cool @davidberenstein1957 !!! Great work.

Only a comment. It would be nice if we add a minimal test for the GET method part.

question: Do we need to change the record_mapper for the rest of the tasks?

[davidberenstein1957]

@frascuchon

I set the record_mapper to be a required variable to make the usage a bit more explicit and avoid potential questions. So, people always need to define a record mapper, especially since using it with ASGI is going to be usecase dependent. For the tests and as examples, I left the current record_mappers within the asgi file.

I will add a GET test.