feat(logs): make gunicorn logs structured

[JacobCoffee]

What

Introduces structured logging for Gunicorn logs

before

web-1           | 192.168.107.1 - - [12/Feb/2025:16:55:43 +0000] "GET /_includes/flash-messages/ HTTP/1.1" 304 0 "http://0.0.0.0/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0"
web-1           | 192.168.107.1 - - [12/Feb/2025:16:55:43 +0000] "GET /_includes/current-user-indicator/ HTTP/1.1" 304 0 "http://0.0.0.0/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0"

after

web-1           | {"logger": "gunicorn.access", "level": "INFO", "event": "192.168.107.1 - - [12/Feb/2025:16:56:00 +0000] \"GET /_includes/flash-messages/ HTTP/1.1\" 304 0 \"http://0.0.0.0/\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0\"", "thread": 281473568329760}
web-1           | {"logger": "gunicorn.access", "level": "INFO", "event": "192.168.107.1 - - [12/Feb/2025:16:56:00 +0000] \"GET /_includes/session-notifications/ HTTP/1.1\" 304 0 \"http://0.0.0.0/\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0\"", "thread": 281473568329760}
web-1           | {"logger": "gunicorn.access", "level": "INFO", "event": "192.168.107.1 - - [12/Feb/2025:16:56:00 +0000] \"GET /_includes/current-user-indicator/ HTTP/1.1\" 304 0 \"http://0.0.0.0/\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0\"", "thread": 281473568329760}

[miketheman]

Very cool! I wonder if this work can also push #16246 forward, so that we'll be able to look at logs locally better?

[JacobCoffee]

@miketheman yeah I can work on that! reading the structured logging stinks locally

[ewdurbin]

That looks rad @miketheman. I'm asking @JacobCoffee to look through other log output (celery for example) from warehouse in general to move it all to structlog initially. Once that's done, the console log option would probably be even more useful!