This function can probably be optimized by using asynchronous RwLock from Tokio instead of blocking one from std, and await lock for the whole connection reset.
However, I didn't have time to play with it so leaving it as-is now and will refactor as a follow-up

Previously we had one channel per connected device. Rabbit docs say:

Given both of these factors, limiting the number of channels used per connection is highly recommended. As a guideline, most applications can use a single digit number of channels per connection. Those with particularly high concurrency rates (usually such applications are consumers) can start with one channel per thread/process/coroutine and switch to channel pooling when metrics suggest that the original model is no longer sustainable, e.g. because it consumes too much memory.