Description of problem:

When entering a custom cluster image set in the UI that doesn't already exist in the hub, the wizard should persist that cluster image set which would allow the user to select it again when creating the cluster.

For example, on a hub where we have imagesets for 4.14.11 and 4.14.12 but NOT OCP 4.14.10, the user can add a custom image set via the release image field:

After the user completes the wizard (successfully or not), then the next the user goes through the wizard the 4.14.10 imageset should appear in the drop down (it does not for hosted cluster):

This behaviour currently exists with the hive cluster creation wizard, and should be consistent.

Version-Release number of selected component (if applicable):

ACM 2.10.0-DOWNSTREAM-2024-02-20-17-59-10

How reproducible:

always

Steps to Reproduce:

1. add new custom imageset via release field in kubevirt creation wizard, go through wizard
2. re-open wizard, expect release image dropdown to have the custom release image
3. observe it does not

Actual results:

Expected results:

Additional info: