Expand entity cache to cover the entire connection

[michaelklishin]

See #579 for background.

RabbitMQ Java client has tweaked its "known entity" tracking to track and invalidate entries in its cache of known entities based on some of their attributes for operations that are performed on the same connection (but any channel on that connection).
In other words, if a queue was declared on one channel but deleted on another channel, it
should not be recovered by automatic connection recovery.

AutorecoveringConnection and AutorecoveringChannel demonstrate the idea.