Status of CMPv2 plugin.name for 2.5 and in the future

[thedatabaseme]

Summary

I've read the issue #11290 and the according PR #11341 which reimplemented plugin.name also for CMPv2 in future versions.
I've understood, that this should be implemented in Argo 2.6, which brings up three questions or proposals to me.

1. Will plugin.name still be specifyable when CMPv1 is removed (planned in Argo 2.7)?
2. The documentation has not been updated to my knowledge, regardless in which version of Argo doc. Or was it?
3. Backport the PR to all Argo versions that support CMPv2. At least Argo 2.5, because this version is now somewhere "inbetween".

Motivation

Having a clear way of implementing CMPv2 in all supporting versions.

Proposal

Backport PR #11341 to Argo 2.5 and update the documentation accordingly. Keep support of specifying plugin.name regardless of the CMP version used for all supported Argo versions.

[crenshaw-dev]

1. Yep!
2. PRs fix: remove argocd-cm plugin warnings #11740 and docs: update config management plugin docs #11690 should cover it I think.
3. I'm not opposed to a backport. It would avoid people having to do 2.5->2.6->2.7 when they'd rather go 2.5->2.7.

@alexmt wdyt?

[jsoref]

@crenshaw-dev: can you please add spaces after the PR numbers in #11751 (comment)