chore: Upgrade Go module to v2

[jannfis]

Fixes #5930

This is one of the recommended approaches given in https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Context (https://github.com/golang/go/wiki/Modules#semantic-import-versioning):

As a result of Semantic Import Versioning, code opting in to Go modules must comply with these rules:

• Follow semver. (An example VCS tag is v1.2.3).
• If the module is version v2 or higher, the major version of the module must be included as a /vN at the end of the module paths used in go.mod files (e.g., module github.com/my/mod/v2, require github.com/my/mod/v2 v2.0.1) and in the package import path (e.g., import "github.com/my/mod/v2/mypkg"). This includes the paths used in go get commands (e.g., go get github.com/my/mod/v2@v2.0.1. Note there is both a /v2 and a @v2.0.1 in that example. One way to think about it is that the module name now includes the /v2, so include /v2 whenever you are using the module name).
• If the module is version v0 or v1, do not include the major version in either the module path or the import path.

Signed-off-by: jannfis jann@mistrust.net

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

[codecov]

Codecov Report

Merging #5931 (f2806ab) into master (d085636) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5931   +/-   ##
=======================================
  Coverage   40.91%   40.91%           
=======================================
  Files         147      147           
  Lines       19635    19635           
=======================================
  Hits         8033     8033           
  Misses      10497    10497           
  Partials     1105     1105           

Impacted Files	Coverage Δ
cmd/argocd-util/commands/app.go	31.71% <ø> (ø)
cmd/argocd-util/commands/argocd_util.go	14.63% <ø> (ø)
cmd/argocd-util/commands/backup.go	0.00% <ø> (ø)
cmd/argocd-util/commands/cluster.go	0.00% <ø> (ø)
cmd/argocd-util/commands/project.go	28.77% <ø> (ø)
cmd/argocd-util/commands/project_allowlist.go	47.29% <ø> (ø)
cmd/argocd-util/commands/repo.go	0.00% <ø> (ø)
cmd/argocd-util/commands/settings.go	68.14% <ø> (ø)
cmd/argocd-util/commands/settings_rbac.go	23.24% <ø> (ø)
cmd/argocd/commands/account.go	0.00% <ø> (ø)
... and 90 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d085636...f2806ab. Read the comment docs.

[sbose78]

Interesting, I wasn't aware of this.

[alexmt]

Borrowed that hack from argo workflows https://github.com/argoproj/argo-workflows/blob/4e450e250168e6b4d51a126b784e90b11a0162bc/Makefile#L323

[alexmt]

LGTM . Thank you @jannfis

[jannfis]

Thanks for collaboration @alexmt