Possible to ack / nack messages that are the incorrect message #1
Description
If client code is handling a message, and we disconnect and reconnect to rabbit. The client code may attempt to ack / nack the message which will now be invalid. The delivery id may be the same as a new delivery just received on the newly reconnected channel.
We need to track delivery id + channel id to assure we do not ack / nack things after its source channel has been disconnected. This will require breaking the RabbitMQ API