Add support for AWS ECR Public credentialprovider

[tvi]

What would you like to be added:
Currently AWS credentialprovider only support ECR in private mode here. These are repositories with suffix amazonaws.com.

I would like to be added support for public.ecr.aws URL as well. This URL works and supports anonymous downloads up to 500GB/month.
Why is this needed:
If there would be public.ecr.aws support in credentialprovider with transparent auth then all downloads within AWS are free.

Here is authentication API for public registries. Its very similar to existing provider.

[k8s-ci-robot]

@tvi: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tvi]

/sig provider-aws

[k8s-ci-robot]

@tvi: The label(s) sig/provider-aws cannot be applied, because the repository doesn't have them

In response to this:

/sig provider-aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tvi]

/sig cloud-provider

[tvi]

/area provider/aws

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten