Robin pilot logging

[Robin-Van-de-Merghel]

Updates to #511 , rebased and linked to #421

[Robin-Van-de-Merghel]

To review this code, this is a summary of what's new compared to the pilot authentification:

• diracx-routers/src/diracx/routers/pilots/logging.py: Upload messages
• diracx-routers/src/diracx/routers/pilot_management/query.py: There's query_logs which helps querying logs with the same idea as job queries
• diracx-logic/src/diracx/logic/pilots/logging.py: Tools to update and query logs
• Modified diracx-testing/src/diracx/testing/mock_osdb.py and util.py to test OSDB with new types: date_nanos. Also added support for queries: returned total (for Content-Range).
• diracx-core/src/diracx/core/models.py: Added logs
• diracx-db/src/diracx/db/*.py: Added logs and updated debug (when we add logs)

[martynia]

I'm wondering why you removed the original line number from the send_message when storing a document. You added a timestamp which is useful, but it might be problematic when sorting messages. The messages should be presented in the order they were emitted by a client.

[Robin-Van-de-Merghel]

I'm wondering why you removed the original line number from the send_message when storing a document. You added a timestamp which is useful, but it might be problematic when sorting messages. The messages should be presented in the order they were emitted by a client.

As timestamps are generated from the pilot itself (as logs are printed out), if we sort logs by timestamps, we could add the right numbering without losing space?

Sorting by timestamp would actually give logs in order they were caught by a pilot, which is what we want? If for whatever reason numbering is broken, we could have shuffled logs, whereas with timestamps we are assured order is kept.

[martynia]

To get the numberring it would be sufficient to define a class variable in the extended logger in the pilot and increment it every time a log statement is called.