Support for the native RabbitMQ connector

The development version of MCollective (2.3.x) only supports 2
connectors: ActiveMQ and RabbitMQ. The Stomp connector has been removed
so there is a need to support native RabbitMQ connector. This patch
generates a rabbitmq.cfg file when connector = 'rabbitmq'.

Along with the removal of the stomp connector, the development version
MCollective has dropped support in the configuration for the topicprefix
parameter.  This patch ensures that the parameter is declared only when
connector = 'stomp'.
Adding identity override on client
Adding support for rabbitmq vhosts
Merging rabbitmq support
Merge pull request #1 from danleyden/rabbitmq

Adding support for rabbitmq vhosts
Merge pull request #3 from simonpasquier/master

Support for the native RabbitMQ connector
Merge pull request #4 from danleyden/master

Adding identity override on client
Bump version and update changelog for release.
Add Berkshelf.
Use vmware for kitchenci.
Fix typo in Fedora yum repo creation.
Add support for v3.0 of the yum cookbook.

Earlier versions are still supported.
Bump version and update changelog.
Merge branch 'yum-3'

Support both new and old versions of the yum cookbook.
Update bundle and add Rakefile for test jobs.
Add Puppetlabs "dependencies" repo on debian/ubuntu.

Without this, the package with the ruby stomp gem can't be found, and
install fails (on 12.04, at least).
Add integration test using activemq

A helper cookbook installs activemq with a suitable configuration.  We
can then test that mcollective is configured and working correctly.
Add a test helper cookbook.

For now, this provides jq (for use by bats), and optionally installs
and configures activemq for use by mcollective.
Merge branch 'activemq_test'

Adds an suite to kitchen that installs activemq and tests
mcollective works end-to-end.
Add a spec for the ::server recipe.