[rabbitmq] Make sure HotBunnies output implementation recovers successfully
[rabbitmq] Make sure HotBunnies output implementation recovers successfully

"Channel alread closed" exceptions are effectively inevitable because
it takes a bit of time to detect network failures, while the pipeline
is pushing data to the output constantly.

So we need to correctly recover from those, too, and set
connection state to true after the exchange is declared.

opentable/logstash-kafka,tinglinux/logstash-kafka,Aloomaio/logstash-kafka,tinglinux/logstash-kafka,joekiller/logstash-kafka,joekiller/logstash-kafka,opentable/logstash-kafka,Aloomaio/logstash-kafka