Match SIP Labels for CAPI Provisioning of Sub-cluster Nodes

[lb4368]

Problem description When SIPCluster CRs are successfully applied to a target k8s cluster for associated sub-clusters, the SIP operator places the following labels on the BMH resources to identify the scheduled BMH resources:

• sip.airshipit.org/cluster-namespace: namespace of SIP CR
• sip.airshipit.org/cluster-name: name of SIP CR
• sip.airshipit.org/node-type: ControlPlane or Worker

These labels need to be matched by CAPI when provisioning the control plane and worker nodes for each sub-cluster.

Proposed change For the multi-tenant type ensure that the controlplane and workers phases for each of the sub-clusters (wordpress & LMA) provision the proper number of appropriate BMH resources by matching labels on the BMH resources with the associated SIPCluster CR namespace/name and the proper node type.

[seaneagan]

Documentation about where to put these labels in the capi resources: https://github.com/metal3-io/cluster-api-provider-metal3/blob/master/docs/api.md#hostselector-examples

[seaneagan]

https://review.opendev.org/c/airship/treasuremap/+/796055