Use --force when creating pacemaker resources

pcs-0.10.14-6 introduced enforce validation at resources creation time.
Unfortunately this doesn't work in our use case as puppet runs on the
host but the necessary binaries are installed inside the containers.

Let's try using --force to workaround.

Conflicts:
	deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml

(wallaby to train)
Conflicts:
	deployment/database/redis-pacemaker-puppet.yaml
	deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml

Closes-Bug: #1997939

Change-Id: Id7616ebceb820d9799661c0fbc5f3f234f421ea3
(cherry picked from commit 59300dfb30)
(cherry picked from commit fde20f941d)
(cherry picked from commit 3fc9478a86)

deployment/database/mysql-pacemaker-puppet.yaml

@@ -185,6 +185,9 @@ outputs:
           - tripleo::profile::pacemaker::database::mysql_bundle::sst_method: {get_param: MysqlGaleraSSTMethod}
             tripleo::profile::pacemaker::database::mysql_bundle::mariabackup_user: {get_param: MysqlMariabackupUser}
             tripleo::profile::pacemaker::database::mysql_bundle::mariabackup_password: {get_param: MysqlMariabackupPassword}
+            # starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
+            # outside the respective containers. we need to use --force to overcome this.
+            tripleo::profile::pacemaker::database::mysql_bundle::force_ocf: true
       # BEGIN DOCKER SETTINGS #
       puppet_config:
         config_volume: mysql

deployment/database/redis-pacemaker-puppet.yaml

@@ -118,6 +118,9 @@ outputs:
                   - 3124
                   - 6379
                   - 26379
+            # starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
+            # outside the respective containers. we need to use --force to overcome this.
+            tripleo::profile::pacemaker::database::redis_bundle::force_ocf: true
             tripleo::stunnel::manage_service: false
             tripleo::stunnel::foreground: 'yes'
             tripleo::profile::pacemaker::database::redis_bundle::tls_proxy_bind_ip:

deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml

@@ -115,6 +115,9 @@ outputs:
                   - 5672
                   - 25672
                   - 25673-25683
+            # starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
+            # outside the respective containers. we need to use --force to overcome this.
+            tripleo::profile::pacemaker::rabbitmq_bundle::force_ocf: true
       service_config_settings: {get_attr: [RabbitmqBase, role_data, service_config_settings]}
       # BEGIN DOCKER SETTINGS
       puppet_config: