Remove deprecated ipv6 corosync parameters

Those are not used anymore since we moved to pcs 0.10/rhel 8 which
uses kronosnet as the default corosync protocol.

In fact corosync_ipv6 in puppet has been removed via
Iaecced845b80e958c7ad0ef96896f1202259cca2 (Fix up cluster_setup_extras
usage)

Change-Id: Icb2bc7cde405584c29ff61609cd104b16ddc67ea
Related-Bug: #1886789

deployment/pacemaker/pacemaker-baremetal-puppet.yaml

@@ -30,10 +30,6 @@ parameters:
   MonitoringSubscriptionPacemaker:
     default: 'overcloud-pacemaker'
     type: string
-  CorosyncIPv6:
-    default: false
-    description: Enable IPv6 in Corosync
-    type: boolean
   EnableFencing:
     default: false
     description: Whether to enable fencing in Pacemaker or not.
@@ -117,23 +113,9 @@ parameters:
     constraints:
       - allowed_pattern: "([1-9][0-9]*s)"
 
-parameter_groups:
-- label: deprecated
-  description: |
-   The following parameters are deprecated and will be removed. They should not
-   be relied on for new deployments. If you have concerns regarding deprecated
-   parameters, please contact the TripleO development team on IRC or the
-   OpenStack mailing list.
-  parameters:
-  - CorosyncIPv6
-
 conditions:
   pcmk_tls_priorities_set:
     not: {equals: [{get_param: PacemakerTLSPriorities}, '']}
-  is_ipv6:
-    equals:
-      - {get_param: [ServiceData, net_ip_version_map, {get_param: [ServiceNetMap, PacemakerNetwork]}]}
-      - 6
 
 outputs:
   role_data:
@@ -161,7 +143,6 @@ outputs:
         pacemaker::resource::bundle::deep_compare: true
         pacemaker::resource::ip::deep_compare: true
         pacemaker::resource::ocf::deep_compare: true
-        corosync_ipv6: {if: [is_ipv6, true, false]}
         tripleo::fencing::config: {get_param: FencingConfig}
         tripleo::fencing::deep_compare: true
         enable_fencing: {get_param: EnableFencing}