Normalize the hardcoded images used for warmpool pre-pulling

[rifelpet]

Fixes #16871

When AWS WarmPool is enabled, nodeup pre-pulls a hardcoded list of images based on the cluster's assets:

https://github.com/rifelpet/kops/blob/4a882890ff2addb1ae0f69f93280102969ab64d3/pkg/nodemodel/nodeupconfigbuilder.go#L490-L507

When a cluster has:

spec:
  assets:
    containerProxy: public.ecr.aws/1234

All of the assets are remapped to begin with the containerProxy value. This results in the WarmPool logic not matching against any of the cluster's assets, and nodeup doesn't treat the instance as being in the warm pool.

Now we run the hardcoded images through the same remapping logic to ensure its matched against any images used in the cluster's assets.

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rifelpet. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rifelpet]

/hold
for manual testing with the e2e job's KOPS_BASE_URL.