Make netty http client resilient to not being closed

[yawkat]

Issue description

The netty implementation of HttpClient starts a netty thread pool. If the client isn't closed, that pool stays alive indefinitely and prevents automatic application shutdown. If we make the pool use daemon threads instead, this might be fixed.

A caveat is connection pooling, not sure how an alive pooled connection would interact with daemon thread shutdown.