Replace stdlib logging with `structlog`

[stevenbal]

Related issue: maykinmedia/objects-api#583

Standard library logging should be replaced with https://www.structlog.org/en/stable/ and useful logging events should be added where they are currently missing

[stevenbal]

@sergei-maertens ter info

[sergei-maertens]

Ah shit I think we had a misunderstanding! At the library level, forcing structlog isn't really the right approach, but I'm not sure what's right either. I think we should check in with @swrichards about our approach here

[sergei-maertens]

I also have thoughts about using a queue and logging worker in a separate thread to address DB transactions and possible performance impact

[swrichards]

I agree that enforcing use of structlog at the level of this library is not what we want, but providing an integration as an optional extra could be good. I have a structlog-friendly handler in gestation here, which we could bundle and expose. If nobody else picks it up I can try and clean it up and put it up for review here.

The question of whether to off-load the logging to a worker seems sensible to me, but orthogonal to this issue.

[sergei-maertens]

I mention it because I want to make sure we don't end up in a situation where that isn't possible anymore.

Let's first have a chat with the three of us to decide how to proceed