Provide v2 of the argocd image tag and refer to it instead of latest

[mikolajprzybysz]

Summary

Provide v2 of the argocd image tag and refer to it instead of latest

Motivation

This PR #7321 has introduced referring to the latest argocd image, which is very problematic, because if you ever deliver argocd image v3 that is not compatible with v2 you will break everyone's setups.

Proposal

As I understand original author intention was to not be forced to update image version with each release and so my proposal will be in this spirit. I suggest to create tag argocd:v2 in quay.io which will target most recent v2 release and refer to it instead of latest. This technique is used across docker hub images.

[jannfis]

Hi @mikolajprzybysz, the image tag is set by Kustomize in the generated manifests that we release. In master branch, it will always be latest, but for the releases, it will have a correct version (refer to the manifests for an example).