Improve ArgoCD Verification Flow

[wandbjake]

Describe the feature you'd like to request

Right now, the ArgoCD agent adds some verification flows automatically. These deploy to argo then check if the application is healthy and synced. However, it is possible that there is a gap between when the sync happens and when the application starts progressing. This can lead to prematurely declaring the app verified.

Describe the solution you'd like to see

Essentially, we need some form of version reporting back from argo, to confirm exactly what is running. This is a little tricky since it can't be done in a generic way. The parameters synced don't always correspond to running container versions, but they would in the case I care about.

A manual way to do it would be to add a way to template version into the verification check, and I can write a per-service call to check if a known container / replicaset is using the expected hash.

Additional information

No response