add customer1-strimzi Flux Kustomization + force:true on customer1

Split Strimzi operator deployment into its own Flux Kustomization so
CRDs are applied before the Kafka CR in customer1.

Chain: infrastructure-controllers -> customer1-strimzi -> customer1

customer1 now has force: true to skip dry-run validation when CRDs are
recently applied but not yet visible to the APIServer cache.

apps/staging/customer1-strimzi/kustomization.yaml

@@ -0,0 +1,5 @@
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+namespace: customer1
+resources:
+  - ../../base/customer1/siriusdevops-db/strimzi

clusters/devops-lab/customer1-strimzi.yaml

@@ -0,0 +1,21 @@
+apiVersion: kustomize.toolkit.fluxcd.io/v1
+kind: Kustomization
+metadata:
+  name: customer1-strimzi
+  namespace: flux-system
+spec:
+  interval: 1m0s
+  retryInterval: 1m
+  timeout: 5m
+  dependsOn:
+    - name: infrastructure-controllers
+  sourceRef:
+    kind: GitRepository
+    name: flux-system
+  path: ../../apps/staging/customer1-strimzi
+  prune: true
+  force: true
+  decryption:
+    provider: sops
+    secretRef:
+      name: sops-age

clusters/devops-lab/customer1.yaml

@@ -8,12 +8,13 @@ spec:
   retryInterval: 1m
   timeout: 5m
   dependsOn:
-    - name: infrastructure-controllers
+    - name: customer1-strimzi
   sourceRef:
     kind: GitRepository
     name: flux-system
   path: ../../apps/staging/customer1  
   prune: true
+  force: true
   decryption:
     provider: sops
     secretRef: