fix(vd): skip terminating PVC when selecting volume migration target

[loktev-d]

Description

In createTargetPersistentVolumeClaim, filter out terminating PVCs before selecting/counting the VD's PVCs, so a still-finalizing source PVC from a previous migration is no longer adopted as the new migration target.

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

When a migration completes, the controller deletes the source PVC but doesn't wait for it to finalize. If the next migration starts within those few seconds, the handler saw 2 PVCs (current + still-terminating old source) and adopted the terminating one as the target. That PVC then disappeared, leaving the VD stuck on "Target persistent volume claim is not found". Surfaced by the e2e StorageClassMigration test.

What is the expected result?

StorageClassMigration e2e test should not fail.

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: vd
type: fix
summary: skip terminating PVC when selecting volume migration target

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