Create namespaces before external secrets

ExternalSecrets are creates at sync-wave "-1" and they are required for
services like Tekton Results and OSP. But for the secrets to be created,
the namespace should exist in advance. Here we create the namespace
before the secret. It does not affect the deployment of the OSP
operator, it ignores the fact the namespace it tries to create already
exist.

operator/gitops/argocd/pipeline-service/openshift-pipelines/kustomization.yaml

@@ -14,3 +14,4 @@ resources:
   - chains-observability-service.yaml
   - chains-public-key-viewer.yaml
   - chains-secrets-config.yaml
+  - namespace.yaml

operator/gitops/argocd/pipeline-service/openshift-pipelines/namespace.yaml

@@ -0,0 +1,10 @@
+# Solves https://issues.redhat.com/browse/PLNSRVCE-1620
+---
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: openshift-pipelines
+  labels:
+    argocd.argoproj.io/managed-by: openshift-gitops
+  annotations:
+    argocd.argoproj.io/sync-wave: "-1"

operator/gitops/argocd/pipeline-service/tekton-results/namespace.yaml

@@ -6,4 +6,5 @@ metadata:
   labels:
     argocd.argoproj.io/managed-by: openshift-gitops
   annotations:
-    argocd.argoproj.io/sync-wave: "0"
+    # Solves https://issues.redhat.com/browse/PLNSRVCE-1620
+    argocd.argoproj.io/sync-wave: "-1"