fix recreate binding on failure

[codomposer]

Fix: Recreate RabbitMQ bindings on connection failure

Fixes

Closes #1469
Closes #1513

Problem

When RabbitMQ goes down and comes back up, the Socket.IO servers enter a split-brain state where they can send events but never receive them. This occurs because:

1. Exchange/queue bindings are created once before the listening loop
2. When RabbitMQ restarts, these bindings become invalid
3. The retry logic reconnects but reuses the stale queue/exchange references
4. Messages can be published (new connections work) but never consumed (old bindings are dead)

This results in servers that appear healthy but silently fail to process incoming events.

Root Cause

When RabbitMQ goes down and comes back up, Socket.IO servers enter a split-brain state where they can send events but never receive them.

Solution

Move the exchange/queue binding creation inside the retry loop so they are recreated on every connection failure.

Result

When RabbitMQ restarts, the exception triggers a retry that creates fresh connection, channel, exchange, and queue objects with valid bindings. Servers can now both send and receive events after recovery.

[miguelgrinberg]

Looks good, thanks!

[julianhille]

when is this going to be released? this is a huge improvement for us apparently.