We want to allow a user to be able to:

1. Perform a full migration so the application and all data is copied to the destination cluster and is running.
2. Allow the end user to test/tweak/validate the application destination cluster so it is running as they need.  (Assume they modified BuildConfigs, tweaked deployments to add resource limits and customized as they want).
3. Allow user to go back to the Migration Plan and re-run a State-Only migration, to resync just the PV data.  The expectation is that the k8s resources on the destination are untouched, the existing PVs are re-used with the data being updated so data on source application is overwritten to destination.  
4. Allow this cycle of test/tweak/validate/resync to happen as many times as desired.

This is intended to only resync PV data.

This is intended ONLY for DVM, not for 'indirect' (Restic), not for Velero.

The k8s resources are intended to be left alone on destination and not adjusted.

The desired effect is that a user can do a migration, test it, and then when happy copy the changed data from the source (production) to the destination.

An alternative to this is to manually run a rsync of source to destination.  We want to make the usage easier from UI.

It is also possible today to perform from UI:

 - Do a Migration

 - Find the associated MigMigration resource that completed and delete it. 

 - Create and run a 'State Only' Migration