Stop using the RABBITMQ_CLUSTERED var and tooling.

credentials: fix tags on requirements install task

It pulls the setting into the comment above it if you do that.

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.

Small doc fix

Fix playbook name

Allow this to be run -c local so you don't need sudo or /usr/bin/python

make databases overridable

Improve RDS cloudmigration documentation

Instead, turn it on for the databases where it makes sense.

fix the permission issue while creating the route53 records

Improvements for s3cmd in the "aws" role

Be able to run jailed code in the CMS as well.

Expose STATICFILES_STORAGE in credentials settings

Work around a supervisord bug causing the provisioning to hang intermittently.

update s3 configuration to use custom credentials s3 backends

New playbook and role for go-server

New playbook and role for go-agent

Install optional credentials requirements

Jibsheet/migrate multiple databases

OPS-727 Sandbox platform name and logo

ECOM-3778

N.B. This may break docker-based devstacks. Fix TBD.