Robust reconnection strategy for amqp and redis
Health checkers in place
Enforce versions on our dependencies
When publishing, acquiring the lock times out after 60 seconds
Enforce strict ordering of processed messages
Tolerence to messages received twice, hardening the reconnection mechanism

To have proper reconnection mechanism, we probably want to move on
celluloid + the new bunny client.
Duplicate messages are just fine in the system

The dependencies logic is more or less symetric in the publisher
model.rb and the subscriber one. Duplicate messages are handled
properly by locking the update in the subscribers side with the
instance row id.
The message synchronizer still takes care of the happen before
relationships.
Version Bump