Description of problem:
https://github.com/konveyor/mig-controller/issues/835

mig-ui is showing a validation failure related to direct migration selections before the user has a chance to select their direct migration settings.

Version-Release number of selected component (if applicable):
1.4.0, latest mig-ui

How reproducible:
Always, in my experience.

Steps to Reproduce:
1. Select namespaces to migrate in mig-ui
2. Proceed to PV discovery step
3. UI will raise error condition warning "Direct image migration is selected and the source cluster openshift-migration/cluster-3 is missing a configured Registry Path"
4. Strangely, the issue seems to be resolved eventually. I checked the spec of the migplan and saw this:

My thought is that the initial migplan created by mig-ui is missing the indirectImageMigration and indirectVolumeMigration settings so the migplan is defaulting to use direct migration.


Expected results:

The migration UI should not throw an error during PV discovery when the user hasn't even had a chance to select indirect/direct migration yet.

This could be solved on controller side by flipping the default and renaming the directImageMigration vars, or it could be fixed in mig-ui by making sure the first version of a migplan that is created has indirectImageMigration and indirectVolumeMigration both set to true.