Goal

Today copy offload configuration pieces don't have validation and users could go wrong about their setup. 

After this epic users will have higher degree of assurance their configuration is valid, more optimized, with more guarantees about the likelihood that the configuration is in place

User Stories

• As an admin configuring MTV and specifically storage offload
    I want MTV to test storage API configuration in a StorageMap so we can catch and correct errors prior to running a plan

• As an admin configuring MTV and specifically storage offload
    I want MTV to validate the storage map has optimal configration so XCOPY/vol-2-vol can work by matching the datastore 
    array backing volume provider with the storageClass CSI provider. Mismatch will lead to fallback, which will still be
    faster, and sometime desirable, but suboptimal. 

• As a user running migrations I want an indication when copy-offload or vddk is in use in the plan view, so users know
    what to expect in terms of time to complete the migrate.

• As a admin configuring migration plans I want a suggestion on the storagemap and the plan to see if my setup can make
    use of offload based on the source datasore and destination storage-class, so migration times will be faster.

  Non-Requirements

• it is not required to include time predictions