fix(vm): fix issue with deleting vmbda from a stopped VM

[LopatinDmitr]

Description

Fixed an issue where VMBDA connected to a VM from VI or CVI disappears from the VM status when it is stopped.

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

Status running VirtualMachine:

blockDeviceRefs:
  - attached: true
    kind: VirtualDisk
    name: vd-root-alpine
    size: 200Mi
    target: sda
  - attached: true
    hotplugged: true
    kind: VirtualImage
    name: vi-root-alpine
    size: 200Mi
    target: sdb
    virtualMachineBlockDeviceAttachmentName: vmbda-vi

Status stopped VirtualMachine:

blockDeviceRefs:
  - attached: false
    kind: VirtualDisk
    name: vd-root-alpine
    size: 200Mi
    target: sda

What is the expected result?

Status running VirtualMachine:

blockDeviceRefs:
  - attached: true
    kind: VirtualDisk
    name: vd-root-alpine
    size: 200Mi
    target: sda
  - attached: true
    hotplugged: true
    kind: VirtualImage
    name: vi-root-alpine
    size: 200Mi
    target: sdb
    virtualMachineBlockDeviceAttachmentName: vmbda-vi

Status stopped VirtualMachine:

blockDeviceRefs:
  - attached: false
    kind: VirtualDisk
    name: vd-root-alpine
    size: 200Mi
    target: sda
  - attached: false
    hotplugged: true
    kind: VirtualImage
    name: vi-root-alpine
    size: 200Mi
    target: sdb
    virtualMachineBlockDeviceAttachmentName: vmbda-vi

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 issue with deleting vmbda from a stopped VM