For QE:

Manual test

Scenario 1: restrictive PSS labels are applied to default ArgoCD instance namespace i.e openshift-gitops

1. Install gitops-operator 1.15.0
2. Verify following labels are added automatically on `openshift-gitops` namespace 

   •         "pod-security.kubernetes.io/enforce":         "restricted",
             "pod-security.kubernetes.io/enforce-version": "v1.29",
             "pod-security.kubernetes.io/audit":           "restricted",
             "pod-security.kubernetes.io/audit-version":   "latest",
             "pod-security.kubernetes.io/warn":            "restricted",
             "pod-security.kubernetes.io/warn-version":    "latest",

1. Update label value
2. The updated lablel value should be reset to original value

Scenario 2: restrictive PSS labels are not applied to non-default ArgoCD instance namespace

1. Install gitops-operator 1.15.0
2. Create a new ArgoCD instance in any namespace other than `openshift-gitops`
3. Verify following labels are not added on the non-default namespace where ArgoCD is installed

   •         "pod-security.kubernetes.io/enforce":         "restricted",
             "pod-security.kubernetes.io/enforce-version": "v1.29",

Upgrade Test

Scenario 1: Upgrade from 1.12 to 1.15

1. Install 1.12 gitops
2. Create a new ArgoCD instance in any namespace other than `openshift-gitops`
3. Verify PSS labels are not present on both `openshift-gitops` and non default ArgoCD namespace
4. Upgrade to 1.15
5. Verify PSS labels are only present on `openshift-gitops`. Below labels should not be added on non-default ArgoCD namespace

   •         "pod-security.kubernetes.io/enforce":         "restricted",
             "pod-security.kubernetes.io/enforce-version": "v1.29",