[ops-messaging] Stop carrying rabbitmq chefspec custom matchers

[Justin Shepherd]

The community rabbitmq cookbook did not have chefspec matchers for its LWRPs until v3.0.2 (https://github.com/opscode-cookbooks/rabbitmq/blob/v3.0.2/libraries/matchers.rb). So we carried them in the ops-messaging cookbook.

Now that these matchers are provided by the upstream cookbook, we no longer need them in the ops-messaging cookbook:

https://github.com/stackforge/cookbook-openstack-ops-messaging/blob/master/spec/support/matcher.rb

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/83838

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/83838
Committed: https://git.openstack.org/cgit/stackforge/cookbook-openstack-ops-messaging/commit/?id=ea38fd69c3a47639f92f1f653be87805b2ce6caf
Submitter: Jenkins
Branch: master

commit ea38fd69c3a47639f92f1f653be87805b2ce6caf
Author: galstrom21 <email address hidden>
Date: Fri Mar 28 12:34:18 2014 -0500

    Remove local rabbitmq lwrp chefspec matchers

    All tests for the rabbitmq lwrps are now using matchers provided by the
    upstream rabbitmq cookbook.

    Change-Id: I60156f22052c625e6d2629b11c0e34463ee8e317
    Closes-Bug: #1299125

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cookbook-openstack-ops-messaging ocata-eol release.