Pass request context to the logger

[mmhand123]

Is your feature request related to a problem? Please describe.
We're trying to integrate handling errors as they come up with sentry and am trying to capture exceptions any time errors come up in TUS. What I've landed on so far, which might not be the best way, is to implement a custom handler for the logger I pass to TUS so that whenever an error log comes in, it captures an exception to Sentry. This works but is missing some request specific context that gets setup when doing routing.

It would be great if logging had access to the request context here.

Describe the solution you'd like
Ideally the logger would have access to the request context via c.log.ErrorCtx (or InfoCtx etc). This way my custom handler can pull out the sentry information from the request context.

Describe alternatives you've considered
Right now it's just capturing generic exceptions, which somewhat works, but is missing important information. Not sure of other ways to achieve what we want but open to any suggestions!

Can you provide help with implementing this feature?
Yes, I can provide a PR if it seems to be a good solution!

[Acconut]

Go's log/slog.Logger provides methods like InfoContext for logging with context. I don't see a reason against using those. Feel free to open a PR to switch tusd's logging to these context-aware functions.

[Acconut]

Implemented in #1237, thank you!