chore: use registry.k8s.io instead of k8s.gcr.io

[34fathombelow]

Signed-off-by: Justin Marquis 34fathombelow@protonmail.com

Proactively updated registry entries that will soon be deprecated.

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

Base: 47.69% // Head: 47.69% // No change to project coverage 👍

Coverage data is based on head (e2715ad) compared to base (974c2de).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #12362   +/-   ##
=======================================
  Coverage   47.69%   47.69%           
=======================================
  Files         246      246           
  Lines       41908    41908           
=======================================
  Hits        19990    19990           
  Misses      19919    19919           
  Partials     1999     1999           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[crenshaw-dev]

Cherry-picked onto release-2.6, release-2.5, and release-2.4.

[occase]

Has this issue been resolved? If not, please let me know which areas need to be worked on..

[crenshaw-dev]

@occase these changes were all made to test data, so I don't think there's a real problem for anyone outside the Argo maintainers. And I believe the maintenance issue (having outdated references in our test data) is resolved. :-)