API reference docs
Release all pending continuations when network failure is detected

This makes it possible for code that uses basic.get and the like to
work with the automatic recovery mode, as well as operations such
as queue.declare to tolerate network splits that happen before
the response is received.
Make writes that fail because of network/socket issues to trigger reconnection/recovery
Fail more gracefully when we get a message on a channel that does not exist

Can be a returned message on a channel that just has been deleted, for
example, or closed due to an exception and removed from the cache.
Support :manual_ack as well as :ack
Set abort on exception for network activity thread
Separate continuations for basic.get operations

Helps support edge cases when blocking operations (e.g. basic.get) are
executed in a tight loop and network recovery has to happen.
If connection is down, make Bunny::Queues#pop return empty responses

To support the same edge case with Bunny::Queue#pop being called
in a tight loop when network connection goes down.

It is better to return something immediately rather than keep
blocking the thread we have no easy way to unblock with the
current "blocking pop" approach that replaces not-entirely-correct
wait/notify implementation.
Spam
Purge the queue first
Move 'basic.get in a tight loop without network connection' workaround to Bunny::Channel#basic_get
API reference docs