feat(vmbda): forbid disk hotplug during migration

[loktev-d]

Description

Forbids hot-plugging a disk into a virtual machine while it is migrating.

Why do we need it, and what problem does it solve?

A volume can only be attached on a single node. Hotplugging one during a live migration pins its PVC to a node and breaks scheduling of the migration target. This change prevents that class of failure by refusing to start a hotplug while the VM is migrating; the attachment simply waits and proceeds automatically once migration completes.

What is the expected result?

With a VM running and an RWO VirtualDisk available (not attached):

1. Start a live migration of the VM.
2. While it is migrating, create a VirtualMachineBlockDeviceAttachment for the disk.
3. The VMBDA stays in Pending with Attached=False / reason BlockedByMigration ("Cannot hotplug a disk while the virtual machine is migrating.")
4. When the migration completes, the VMBDA is re-reconciled and transitions to Attached.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vmbda
type: feature
summary: forbid disk hotplug during migration

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.