Develop a migration strategy for ArgoCD

[lisac]

After establishing svc-bip-api as VRO's first app deployable in ArgoCD, we should determine a strategy for rolling out the ArgoCD deployment option for other apps on VRO; and a strategy for deprecating use of non-ArgoCD deployments. Additionally, we should ensure the partner teams have visibility into these changes.

Acceptance criteria

1. a prioritized list of VRO apps to be made available for deployment in ArgoCD
2. a strategy for deprecating use of non-ArgoCD deployments
3. a decision on when to address Configure ArgoCD + Vault for svc-bip-api #3037
4. documentation to account for complexities in troubleshooting deployments. for example: how does one figure out which platform did the deployment (ArgoCD or non-ArgoCD)?

Notes about work

• depends on completion of Configure ArgoCD svc-bip-api for Prod cluster #3041
• consider implementing a CODEOWNERS on va-abd-rrd-argocd-applications-vault - why: to support partner teams configuring deployments on their own apps while not disrupting affecting apps of other partners

[lisac]

To support the rollout, here are placeholder tickets for the remaining apps:
(not in priority order)

• Configure ArgoCD for svc-bie-kafka #3086
• Configure ArgoCD for svc-bgs-api #3087
• Configure ArgoCD for dev-tools #3088
• Configure ArgoCD for db-init #3089
• Configure ArgoCD for rabbitmq #3090
• Configure ArgoCD for domain-xample #3091
• Configure ArgoCD for Contention Classification (CC) #3092
• Configure ArgoCD for EP Merge (EE) #3093
• Configure ArgoCD for Max CFI (EE) #3094