NOTE: we can not merge this until FR3 branch is created upstream.

Goal: 

Once watcher is integrated into openstack-operator, all Watcher deployment jobs should be moved to use openstackcontrolplane instead of directly creating Watcher CR.

Ideally we should implement this in a backwards compatible way so that deployment jobs would work with both the "standalone" and "integrated" modes:

• If watcher-operator is deployed together with the openstack-operator, we should apply a kustomize to the controlplane to include the deployment of watcher. We may test this by inspecting the openstackcontrolplane CRD (if there is watcher service on it). If there is no watcher on it , do not apply that kustomization. Note we need the openstack operator to be installed before checking this
• If the watcher-operator is deployed with the openstack-operator, we can totally skip the deploy_watcher post_deploy hook. Otherwise, run it.

That's a possible approach, other may exist, but the high level goal is to be able to run deployment jobs in both modes to ease the migration both upstream and downstream.