Request logging

Nobody has claimed this yet.

Basically we want per-request logging where logs that happen within a Express request can be correlated together (span). We need to store a request ID in the context of a request and be able to get the request ID without needing to pass around `request` everywhere.

- https://www.izertis.com/en/-/blog-express-js-logging-info-with-global-unique-request-id-node-js
- Talks about using [`express-http-context`](https://www.npmjs.com/package/express-http-context) and wrapping `winston` to include the request ID in the logs
- Uses `cls-hooked` under the hood which is "Continuation-Local Storage" and the equivalent to "Thread Local Storage" (TLS) for Node.js in the call stack context (and `async_hooks`).
- https://javascript.plainenglish.io/simple-request-specific-logging-for-node-js-212bb2c0e887
- [`async_hooks`](https://nodejs.org/docs/latest-v16.x/api/async_hooks.html) are still "[Stability: 1](https://nodejs.org/docs/latest-v16.x/api/documentation.html#stability-index) - Experimental",
- Links to an interesting performance analysis about the performance hit when using `async_hooks`, https://github.com/bmeurer/async-hooks-performance-impact

Start by reading the repository's Express request-handling and logging entry points, then compare the referenced express-http-context, cls-hooked, winston, and async_hooks approaches. The issue is complete when request IDs can be stored per request and included in correlated logs without passing request through every call, with the performance tradeoff addressed.

Written by the indexing model from the issue text.