fix(vm): fix affinity when migrating VM with local disks

[loktev-d]

Description

Fixes intermittent unschedulable migration of VMs with local-storage disks attached via VMBDA. Three coordinated changes:

1. state.go (resolvePVCName / PVNodeAffinityTerms) — during a volume migration, derive the VM pod's node affinity from the migration target, never the source PVC's bound node.
2. migration_volumes.go (SyncVolumes) — when volumes are already synced but the affinity drifted, re-patch it.
3. kvvm_utils.go (syncAttachedVMBDAHotplugVolumes) — skip disks that are migrating, leaving their hotplug volume to the migration flow. Prevents the main sync from reverting the hotplug volume to the source PVC.

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

Migrating a VM with local disks attached through VMBDA failed intermittently . The migration target pod was pinned to the source node — KubeVirt copies the VM-pod node affinity and forbids the source node via anti-affinity, so the pod was unschedulable and the migration timed out.

What is the expected result?

A VM with VMBDA-attached local-storage disks evicts/migrates reliably

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: vm
type: fix
summary: fix affinity when migrating VM with local disks

[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.