Align ECR image path with Kubernetes community registry

[torredil]

Currently, there's an inconsistency between the image paths for the EBS CSI driver in different registries:

• KCR: registry.k8s.io/provider-aws/aws-ebs-csi-driver
• ECR: public.ecr.aws/ebs-csi-driver/aws-ebs-csi-driver

This discrepancy causes issues in testing environments that use registry mirroring or substitutions.

In the long term, it would be desirable to align the ECR path with the community registry by migrating to a provider-aws repository in ECR to eliminate these errors in testing and deployment scenarios.

Additional context

See kubernetes/test-infra#33061 for more context.

/priority/important-longterm

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale