When register mirror is used creating a cluster shows error messages and the pods under eksa-packages have `ImagePullBackOff`status

**What happened**:

```
2022-10-24T20:44:47.604Z V6 waiting for package bundle controller to activate a bundle {"clusterName": "rbxop-cs-dev-isc-mgmt"}
2022-10-24T20:44:48.605Z V6 Executing command {"cmd": "/usr/bin/docker exec -i eksa_1666643431596400617 kubectl get --ignore-not-found -o json --kubeconfig rbxop-cs-dev-isc-mgmt/rbxop-cs-dev-isc-mgmt-eks-a-cluster.kubeconfig packageBundleController --namespace eksa-packages rbxop-cs-dev-isc-mgmt"}
2022-10-24T20:44:49.017Z V6 waiting for package bundle controller to activate a bundle {"clusterName": "rbxop-cs-dev-isc-mgmt"}
...
2022-10-24T20:45:13.372Z V0 ❌ Error when installing curated packages on workload cluster; please install through eksctl anywhere install packagecontroller command {"error": "context deadline exceeded"}
2022-10-24T20:45:13.372Z V0 ❌ Curated Packages Installation Failed...
2022-10-24T20:45:13.372Z V4 Task finished {"task_name": "install-curated-packages", "duration": "1m8.807321401s"}
```

```
$ KUBECONFIG=mgmt/mgmt-eks-a-cluster.kubeconfig kubectl get po -n eksa-packages
NAME READY STATUS RESTARTS AGE
eks-anywhere-packages-56c78c6746-jbz6w 0/1 ImagePullBackOff 0 5m24s
eksa-auth-refresher-nh2d9 0/1 ImagePullBackOff 0 5m23s
```

**What you expected to happen**:
No error messages should occur when creating a cluster with a register mirror.
All pods should be successfully installed and running after creating a cluster with a register mirror

**How to reproduce it (as minimally and precisely as possible)**:
Create a mgmt cluster with register mirror

**Anything else we need to know?**:
This issue does *not* occur when a register mirror is not used. This occurs only if a register mirror is used when creating a cluster.

**Environment**:
- EKS Anywhere Release: 0.12.0
- EKS Distro Release:

Start by reproducing management-cluster creation with a registry mirror on EKS Anywhere 0.12.0 and inspect the `install-curated-packages` step. Check `kubectl get po -n eksa-packages` and the package bundle controller, then compare the behavior with and without a registry mirror. Done means cluster creation completes without the timeout and the package pods are running rather than in `ImagePullBackOff`.

Written by the indexing model from the issue text.