kubevirt-dm: Async BIA which creates DU

[weshayutin]

BIA that is triggered with kubevirt dm policy

Description:
VirtualMachine BIA which checks preconditions (incremental backup enabled, snapshot-move-data set, matching kubevirt volume policy), creates DU, and monitors DU progress.
See "BackupItemAction/RestoreItemAction plugins" section of #2037

Subtasks:

DOD:

[shubham-pampattiwar]

Integration Requirements from kubevirt-datamover-controller (Phase 2)

The controller (PR: migtools/kubevirt-datamover-controller#4) expects the BIA plugin to set the following when creating the DataUpload:

Required Annotations:

metadata:
  annotations:
    kubevirt-datamover.io/vm-name: "<source-vm-name>"
    kubevirt-datamover.io/vm-namespace: "<source-vm-namespace>"

Required Spec Field:

spec:
  datamover: "kubevirt"

What the Controller Creates:

Resource	Name Pattern	Namespace
Temp PVC	kubevirt-backup-<dataupload-name>	VM's namespace
VirtualMachineBackupTracker	<dataupload-name>-vmbt	VM's namespace
VirtualMachineBackup	<dataupload-name>-vmb	VM's namespace

Phase Flow:

New → Accepted → Prepared → InProgress → Completed

• At Prepared phase: VMB completed, qcow2 backup data is in the temp PVC
• Phase 3 (InProgress → Completed) data movement not yet implemented

Dependency Note:
Controller uses kubevirt.io/api v1.8.0-alpha.0 for VirtualMachineBackup/VirtualMachineBackupTracker types (will update to stable when v1.8.0 releases).

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale