ArgoCD + Adopt GitOps

By adopting GitOps (https://www.redhat.com/en/topics/devops/what-is-gitops) we are able to achieve the following results
- easier code readability
- devops single source of truth
- easier developer onboarding
- access to k8s auditing tools

Some example tools:

- [kubeaudit](https://github.com/Shopify/kubeaudit)
- [checkov](https://www.checkov.io)
- [snyk](https://docs.snyk.io/products/snyk-infrastructure-as-code/scan-kubernetes-configuration-files/scan-and-fix-security-issues-in-helm-charts)

**Discussed Nov 30 2022:**
- Let's see if we can get a demo from someone with knowledge of Argo -> (devops guild?)
- Replacing the current infrastructure will be a big lift
- We should consider using this for a new project

#### Checklist
- [ ] reach out to someone/team who uses ArgoCD
- [ ] have demo
- [ ] discuss/document pros/cons of implementing and impacts

Start by reviewing the GitOps overview and the linked kubeaudit, checkov, and Snyk examples, then identify someone or a team with ArgoCD experience for the requested demo. Document the pros, cons, implementation impacts, and whether a new project is the right scope; completion also requires checking off the outreach and demo steps.

Written by the indexing model from the issue text.