[Umbrella issue] Migrate from k8s.gcr.io to registry.k8s.io

[ameukam]

Part of:

• Umbrella issue: k8s.gcr.io => registry.k8s.io solution #1834

Design doc: https://docs.google.com/document/d/1yNQ7DaDE5LbDJf9ku82YtlKZK0tcg5Wpk9L72-x2S2k.

This issue focus on the implementation of oci-proxy as a proxy/redirect endpoint for k8s.gcr.io:

Sandbox environment

• Setup a sandox environment for development: registry-sandbox.k8s.io.
  • Build sandbox infrastructure for oci-proxy #3317
  • Stress of registry-sandbox.k8s.io registry.k8s.io#16
• Migrate test workloads to registry-sandbox.k8s.io:
  • Add more env vars to preset-pull-registry-sandbox-repo-list test-infra#25466
  • Add a GCE e2e optional presubmit to test registry sandbox test-infra#25458
  • Switch on new registry for pull-kubernetes-e2e-gce-ubuntu-containerd test-infra#25608
  • Switch to registry.k8s.io from registry-sandbox test-infra#25607

Production environment:

(taken from #1834 (comment))

• Continuous deployment
• Monitoring: Cloud Run provides native metrics based on GCP Monitoring: https://cloud.google.com/run/docs/monitoring
• Logging: built in archeio and using Cloud Logging
• PII Management: Using Linux Foundation privacy policy: https://regisry.k8s.io/privacy
• Recovery
• Scalability: Cloud Run auto-scaling
• Incident Management

/milestone v1.24
/priority important-soon

cc @BenTheElder @dims @eddiezane