Add manage_service settings to get puppet out of the way.

This should make starting services more consistent, as pacemaker will have full control of starting and stopping the services without the chance of puppet having already done so, which potentially
could cause confusion for pacemaker.
pacemaker did not bring up rabbitmq across all nodes after a couple of fresh attempts. E.g.:

    # pcs status
    Clone Set: rabbitmq-server-clone [rabbitmq-server]
    Started: [ c1a1.example.com c1a2.example.com ]
    Stopped: [ c1a3.example.com ]

From the puppet output on the control node:

    Debug: Execone-time-rabbitmq-server-disable: Executing '/sbin/chkconfig rabbitmq-server off'
    Debug: Executing '/sbin/chkconfig rabbitmq-server off'
    Notice: /Stage[main]/Quickstack::Pacemaker::Rabbitmq/Quickstack::Pacemaker::Manual_service[rabbitmq-server]
    /Exec[one-time-rabbitmq-server-disable]/returns: executed successfully
    Debug: /Stage[main]/Quickstack::Pacemaker::Rabbitmq/Quickstack::Pacemaker::Manual_service[rabbitmq-server]
    /Exec[one-time-rabbitmq-server-disable]: The container Quickstack::Pacemaker::Manual_service[rabbitmq-server] will propagate my refresh event
    Debug: Quickstack::Pacemaker::Manual_service[rabbitmq-server]: The container
    Class[Quickstack::Pacemaker::Rabbitmq] will propagate my refresh event
    Debug: /usr/sbin/pcs resource show rabbitmq-server > /dev/null 2>&1
    Debug: /usr/sbin/pcs resource create rabbitmq-server systemd:rabbitmq-server op monitor interval=30s start-delay=35s interval=30s --clone
    Error: Unable to create resource/fence device
    Call cib_create failed (-206): Application of an update diff failed

If I comment out the above 3 lines quickstack::pacemaker::manual_service { "rabbitmq-server":..., rabbitmq comes up fine for me.

    Clone Set: rabbitmq-server-clone [rabbitmq-server]
       Started: [ c1a1.example.com c1a2.example.com c1a3.example.com ]

The cause isn't clear to me, but I've got the logs handy.