Deploy Synclabeller Operator via Airship Phase in multi-tenant type

[lb4368]

Problem description When creating sub-clusters for a site, the SIP operator uses labels on BMH resources to schedule matching resources to a sub-cluster. To expand this selection criteria, labels assigned to Kubernetes nodes can be made available on corresponding BMH resources using the Synclabeller operator. As an operator, I want to deploy the Synclabeller operator as part of a multi-tenant site during an airshipctl phase, so that all node labels are available as BMH selection criteria for SIPCluster CRs.

Proposed change Deliver the Synclabeller operator to the target/management cluster as part of an airshipctl phase. Upon completion of this phase the operator is deployed and ready for use.

1. Integrate the delivery of the Synclabeller CRD/operator (https://github.com/airshipit/synclabeller) into an Airship phase defined in the multi-tenant type manifests.
2. Verify capability to run phase applying operator via Airship.

[lb4368]

PS here: https://review.opendev.org/c/airship/treasuremap/+/785834

[digambar15]

PS is passing zuul. Please review.

[digambar15]

Please assign issue to me.

[digambar15]

PS merged - https://review.opendev.org/c/airship/treasuremap/+/785834

[jezogwza]

This PS merged. Closing.