fix(vm): show CSI and volume errors in VM status

[loktev-d]

Description

Fix VM status to properly display CSI driver and volume attachment errors
Fix misleading errors related to SDN ("waiting for SDN module")

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

When a VM fails to start due to CSI driver issues (e.g., missing CSI driver, volume attachment failures), the VM status shows incorrect error messages: "Cannot determine the status of additional interfaces, waiting for a response from the SDN module". The actual CSI error was hidden in pod events and not surfaced in the VM status.

What is the expected result?

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: show CSI and volume errors in VM status

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