chore: migrate from k8s.gcr.io to registry.k8s.io

[ahmedwaleedmalik]

Description

Kubernetes is migrating its image registry from [k8s.gcr.io](http://k8s.gcr.io/) to [registry.k8s.io](http://registry.k8s.io/).

Part of kubernetes/k8s.io#4780.

It's just changing some testing/fixture data so it's a benign change but I made it anyways.

Related Issue

Motivation and Context

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[gaius-qi]

LGTM

[jim3ma]

LGTM

[codecov]

Codecov Report

Merging #2186 (c765bf7) into main (d1388ff) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2186      +/-   ##
==========================================
+ Coverage   48.24%   48.25%   +0.01%     
==========================================
  Files         141      141              
  Lines       19668    19668              
==========================================
+ Hits         9489     9491       +2     
  Misses       9591     9591              
+ Partials      588      586       -2     

Flag	Coverage Δ
Object-compatibility-e2etests	?
e2etests	?
unittests	48.25% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes