Add context information to each log message in authenticated endpoints

[GianlucaFicarelli]

Add context information to each log message in authenticated endpoints.
It shold be used only in authenticated endpoints, since it depends on user_context.
These additional keys are added to the extra dict:

• sub_id: the subject_id from Keycloak
• request_id: id that can be used to correlate multiple logs in the same request
• forwarded_for: the originating IP address of the client, from the X-Forwarded-For HTTP header

This PR also adds 2 headers to the response:

• x-process-time: process time in seconds, formatted
• x-request-id: the request id, server generated. If the header is present also in the request headers, its value is ignored to ensure that is unique on the server side, but this can be discussed.
• We could decide to add also a header X-Correlation-ID to trace the transaction end-to-end across multiple services, but need more considerations and changes.

Example of the added response headers:

< x-request-id: 87746ace-9e21-4879-bfee-bbf4f7c7e300
< x-process-time: 0.868

Fix https://github.com/openbraininstitute/prod-platform-architecture/issues/187

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
pytest	97.68% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
app/application.py	96.96% <100.00%> (+1.05%)	⬆️
app/dependencies/logger.py	100.00% <100.00%> (ø)
app/routers/__init__.py	100.00% <100.00%> (ø)
app/schemas/types.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mgeplf]

that's so beautiful