MCO select an incorrect default AMI: the AMI in {{us-east-1}} was selected for the cluster in {{us-east-2}}

Here is the test process:

 * Download OKD installer via `oc adm release extract --tools registry.ci.openshift.org/origin/release-scos:4.19.0-0.okd-scos-2025-06-12-164744` and install OKD cluster in `us-east-2`

 * us-east-2 for OKD is not native support region, which means the bootimage will be copied from us-east-1 during installation process:

./openshift-install coreos print-stream-json | jq -r --arg r us-east-2 '.architectures.x86_64.images.aws.regions[$r]'
null

./openshift-install coreos print-stream-json | jq -r --arg r us-east-1 '.architectures.x86_64.images.aws.regions[$r]'
{
  "release": "9.0.20250510-0",
  "image": "ami-0c4afb3332ab4602d"
}

install log:
level=info msg="Copying AMI ami-0c4afb3332ab4602d to region us-east-2"

 * Cluster was installed successfully
 * Checking the machineset, the AMI image is the default image in us-east-1, which is not exit in us-east-2

oc get machineset.machine.openshift.io -n openshift-machine-api -A -ojson | jq -r '.items[] | .spec.template.spec.providerSpec.value.ami.id' | sort | uniq
ami-0c4afb3332ab4602d

4.19.0-0.okd-scos-2025-06-12-164744
    

Always
    

    1. See description 
    2.
    3.
    

The issue was originally discussed in https://issues.redhat.com/browse/OCPBUGS-57348?focusedId=27405648&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27405648   

OCP will hit the same issue if the RHCOS AMI does not exist in the target region.