pacemaker: increase timeouts for rabbitmq and redis

When we observe the 'stop timeout' values of pacemaker resources:
rabbitmq and redis, they are set to 90s. But for all other services, it
is set to 200s.
The overcloud deployment sometimes fails due to this with the error:
Error: Could not complete shutdown of rabbitmq-clone, 1 resources
remaining
Error performing operation: Timer expired

This patch updates the timeout for Redis and RabbitMQ to avoid this
error.

Change-Id: I8a3b3951a896ee3e8e5e09778e8ea4717e76a1b4

manifests/profile/pacemaker/database/redis.pp

@@ -60,6 +60,7 @@ class tripleo::profile::pacemaker::database::redis (
       master_params   => '',
       meta_params     => 'notify=true ordered=true interleave=true',
       resource_params => 'wait_last_known_master=true',
+      op_params       => 'start timeout=200s stop timeout=200s',
       require         => Class['::redis'],
     }
   }

manifests/profile/pacemaker/rabbitmq.pp

@@ -86,6 +86,7 @@ class tripleo::profile::pacemaker::rabbitmq (
       resource_params => "set_policy='ha-all ^(?!amq\\.).* {\"ha-mode\":\"exactly\",\"ha-params\":${nr_ha_queues}}'",
       clone_params    => 'ordered=true interleave=true',
       meta_params     => 'notify=true',
+      op_params       => 'start timeout=200s stop timeout=200s',
       require         => Class['::rabbitmq'],
     }
   }