clouddbs are currently getting tagged with cluster: mysql

There are actually 4 different Hiera tags we should check for clouddb hosts (see T375673: Define single hiera key to identify WMCS-managed bare metal hosts):

• profile::admin::groups: this is set to wikireplicas-roots and it can stay like that (see T344599: wikireplicas root access)
• contactgroups: I suggest we set it to wmcs-team-email
• cluster: I suggest we set it to wmcs
• profile::contacts::role_contacts: this is currently set to ['Data Platform','WMCS'], we should set it to WMCS only

I'm not entirely sure about Icinga alerts for clouddb* hosts. As far as I understand it:

• emails and pages sent by Icinga are routed based on the value of contactgroups (current value: admins, I think)
• alerts that are forwarded from Icinga to Alertmanager are tagged with team=wmcs based on the regex in icinga_exporter.yaml

We discussed this today with @Marostegui and @joanna_borun and we agreed that the following alerts should exist and should be routed to the WMCS team for clouddb* hosts:

• mysql down
• replication broken
• replication lag greater than x

All these alerts should be critical but not paging.