Updating with patterns used in ops-database

We had two reviews which added an ops-messaging cookbook.  Updating
this cookbook with patterns we estabished from the database cookbook.
Craig already did most of the work, however, updated the tests to
use the chefspec find_provider, added clustering support, and attempted
to follow the service_type attribute patterns used in database cookbook.
Since these cookbooks are not complete, added a larger commit than
would have.

Change-Id: I0edfc996df413c6e41a31d53f964d7f5fc9e0aeb
Moved clustering setup to an attribute

Clustering is set to false by default.  When enabled, will setup
rabbitmq disk node clustering.  Also, added opscode to attribution,
somehow had removed them in the previous rebase.

Change-Id: Idd249d0d950f5f4eb44cd7c10566ece254ed7f45
Removed default recipe

Should be specifying the server recipe, and
not have a default recipe.

Change-Id: I9685fbac64f93eac3b9e6a9451d9e948225f3c49
Removed attributes now handled by `openstack-common`

Now that `openstack-common` handles the `["openstack"]["mq"]`
attributes, there is no need to set them in the default test cases.

Change-Id: I1987a6c4ae0898bcf2cd0100fd1f5408990f2592
Merge "Removed default recipe"
Merge "Removed attributes now handled by `openstack-common`"
Searching on wrong environment

We need to use chef_environment vs environment.

Change-Id: I2ceba5a49ec88f81ad763379bebbd63d9bd19bb8
The upstream cookbook already resets rabbit

No need to do what upstream already does.
  https://github.com/opscode-cookbooks/rabbitmq/blob/master/recipes/default.rb#L136

Change-Id: I549558a4b8cf45902389a06041bf846e16290386
Sort the results

Results need to be sorted.  OpenSource Chef 11 doesn't preserve order.

Change-Id: I00e649f1833915f6372d7d59dcefc6c073aca29f
Removed unused attributes from README

These attributes are specified in openstack-common.
Don't see why we should document them inside the wrapper,
should only document attributes the wrapper is setting

Change-Id: Ic4be7505348e0a2d52442f64bcf388f2244e11e6
Merge "Sort the results"
Configure rabbit and EPMD to bind to an address

This change integrates against a rabbitmq cookbook feature which
is not yet merged upstream.  However, given the default code path
does not change, felt okay to get this out there.  Especially b/c
we are dependant on it.  This feature allows one to run rabbit
and clustering across a specific address.  For more details, see:
  http://tickets.opscode.com/browse/COOK-3320

Change-Id: I2a10c551cb2176dadaee8842eeadfdfc8cb93e44
Revert "Configure rabbit and EPMD to bind to an address"

Since this breaks people using rabbit in the standard way, I
rather revert this change, and fork my own ops-messaging cookbook
since this is intended as an example cookbook (granted others
may use it directly).  This code would be better off in my
own fork, where i do not impact others, with a non-merged upstream
rabbitmq feature.

This reverts commit 3b35ac204d7b117e86cc51d72bfc4a927183a92a.

Change-Id: I53da70583c50ae985d3842c3d709eb81f565d63d
update to use openstack-common 0.4.0

Change-Id: I2bf08ba0fe085852e9171c674c9a4eed15c48496