Set appropriate policy for mirrored queues

Previously, the config_mirrored_queues parameter
had no effect. This patch adds a policy defined type
and if mirroring is requested, an appropriate
policy is created. The README has been updated to
clarify the case where this is applicable.
Set HOME env variable to nil when leveraging rabbitmq to remove type error from Python script
$stomp_ensure is boolean and the type does not accept true or false as a valid ensure value
Merge pull request #205 from bezerker/master

Resolve rabbitmq_exchange type error
Merge pull request #171 from michaeltchapman/mirrorqueue

Set appropriate policy for mirrored queues
Revert "Set appropriate policy for mirrored queues"
Merge pull request #214 from puppetlabs/revert-171-mirrorqueue

Revert "Set appropriate policy for mirrored queues"
document a bunch of missing parameters
MODULES-1242 add spec and acceptance tests for rmq 2.8.1 and credentials in rabbitmqadmin URL, and README note on RedHat upgrade/downgrade issues
MODULES-1242 Add credentials to rabbitmqadmin URL and fix some spec tests for this
autorequire service

Signed-off-by: Stephen Gran <stephen.gran@piksel.com>
Merge pull request #221 from jantman/MODULES-1242

Modules-1242 always use credentials in rabbitmqadmin URL
Merge pull request #219 from jantman/paramdoc

document a bunch of missing parameters
Merge pull request #206 from bezerker/ruby-stomp

Use valid ensure value similar to ldap_auth when stomp_ensure = true
Merge pull request #222 from sgran/master

autorequire service
rabbitmq::manage_repos sets 'ensure' in apt::source

The ensure paramenter in apt::source is set to 'present' or 'absent'
based on the value of rabbitmq::manage_repo.
Added rspec tests for previous commit 4dad6be
Rename variable 'manage_repos' to 'repos_ensure'

'manage_repos' doesn't describe the intended behaviour of the variable.
We decided to rename it to 'repos_ensure'. This will break backward
compatibility.