Do not force the provider to 'rabbitmqctl'
Do not force the provider to 'rabbitmqctl'

There is no need to force the provider to 'rabbitmqctl' as the
puppet-rabbitmq module only has that as a provider.
We need to allow the operator to override the provider so
we can use this manifest with custom tags and a noop provider
to run inside containers.

vtas-hyperscale-ci/puppet-veritas_hyperscale,vtas-hyperscale-ci/puppet-veritas_hyperscale,vtas-hyperscale-ci/puppet-veritas_hyperscale