Data Mover restore integrate to VolumePopulator

[Lyndon-Li]

Basically, the current data movement design #5968 is compatible with the VolumePopulator workflow, but there are some gaps to fully integrate with VolumePopulator, i.e., it is not using DataSourceRef for PVC-PV matching.

Since VolumePopulator is already a Beta feature, it's better we have both mechanism:

• The existing mechanism as mentioned in Volume Snapshot Data Movement Design #5968 to support older version of Kubernetes
• The VolumePopulator mechanism to support newer versions of Kubernetes

So, let's do it post-1.12

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[Lyndon-Li]

With some adjustment and enhancement, the current data mover restore workflow is fully compatible with VolumePopulator in 1.12, the only gap is that is not using DataSourceRef but using the PVC match label selector instead, which is tracking by #6018, so we can close this issue now and use 6018 to track the DataSourceRef changes.