Update LMA sub-cluster CAPI namespace

All KubeadmControlPlane, Metal3Cluster, and Metal3MachineTemplates must reside in
the same namespace to which ViNO applies BMH objects. This change
updates the LMA sub-cluster CAPI namespace reference within the
airhsipctl cluster map to vino-system, where all of those objects
reside. This change also modifies the Kustomiza entrypoints that deploy
CAPI objects to deploy them into the same namesapce.

Signed-off-by: Drew Walters <andrew.walters@att.com>
Change-Id: Ie8f8516326d505c290d6d4ac04ef50fa900e62da

manifests/type/multi-tenant/phases/cluster_map_patch.yaml

@@ -28,7 +28,7 @@ map:
         clusterAPI:
           clusterNamespacedName:
             name: lma
-            namespace: lma
+            namespace: vino-system # All CAPI objects reside in the vino-system namespace
       # NOTE: This context does not exist unless added on disk manually. This
       # entry is here for backup.
       - type: "filesystem"

manifests/type/sub-cluster/controlplane/kustomization.yaml

@@ -10,3 +10,6 @@ patchesJson6902:
     kind: Metal3MachineTemplate
     name: cluster-controlplane
   path: patches/metal3machinetemplate.yaml
+
+# NOTE: CAPI objects must be in the same namespace in which ViNO applies BMHs.
+namespace: vino-system

manifests/type/sub-cluster/workers/kustomization.yaml

@@ -4,3 +4,6 @@ resources:
   - kubeadmconfigtemplate.yaml
   - machinedeployment.yaml
   - metal3machinetemplate.yaml
+
+# NOTE: CAPI objects must be in the same namespace in which ViNO applies BMHs.
+namespace: vino-system