Namespace isolation for ClusterSecretStore with core secrets

[all4code]

Implement namespace isolation for following best practices

Allow only access to the vault-kv-secret ClusterSecretStore only from argo, argocd, atlantis, github-runner, harbor, monitoring, oauth2-proxy, sonarqube namespaces

cg-devx-core/platform/gitops-pipelines/delivery/clusters/cc-cluster/core-services/components/kube-system/cluster-secret-store/clustersecretstore.yaml

Line 4 in 542b285

name: vault-kv-secret

Create a clone of secrets ci-secrets&proxy-docker-config in the vault-kv-workloads-secret ClusterSecretStore

Modify workload templates to use ci-secrets & proxy-docker-config from the workload’s ClusterSecretStore