RABBITMQ_CLUSTERED was removed and rabbitmq_clustered_hosts was renamed.

This method relied on the `hostvars` variable provided by ansible to always
be all the nodes in the rabbitmq cluster.  The hostvars var broke as a result
of the upgrade to ansible 1.9 but also even if it did work, this method
required that you always run rabbit plays on the whole cluster.  This is not
reasonable as it makes it very hard to heal a single node that may have fallen
over.

From here on, the RABBITMQ_CLUSTERED_HOSTS var should be used instead to
specify the rabbit hosts that are part of a cluster.

Alsa, add connection logging to rabbitmq.

* Create an upstart job that is run after supervisor stops to sync logs
* Syncs trakcing logs before application logs
* stderr and stdout go to /dev/null so we don't fill up root's mailbox

In order to support --check we need to ensure that registered
vars exist before checking their stdout. Otherwise ansible
errors out.

Also renaming the deploy_* plays to the play name