[controller] Add BlockDevice resource selector for LVMVolumeGroups

[ViktorKram]

Description

1. The LvmVolumeGroup kind is renamed to LVMVolumeGroup kind.
2. Added the spec.blockDeviceSelector field to LVMVolumeGroup resources.
3. Removed the spec.blockDeviceNames field from LVMVolumeGroup resources (now you specify the BlockDevice resources through the selector).
4. Added the spec.local field.

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

1. The LvmVolumeGroup kind is renamed to LVMVolumeGroup kind.
   This is needed for better code style and code consistency. To achieve this, the controller will provide a migration to replace the old LvmVolumeGroup CRD with the new LVMVolumeGroup one. Every LvmVolumeGroup resource will be migrated as well, changing its kind to LVMVolumeGroup with new spec functionality.

2. BlockDeviceSelector field in LVMVolumeGroup resource's spec.
   This feature allows users to specify a selector for BlockDevice resources, which will be used to configure the LVMVolumeGroup. The selector field replaces the old spec.blockDeviceNames field, providing an opportunity to fully configure the LVMVolumeGroup resources while bootstrapping a cluster. It is also a more flexible way to operate with BlockDevice resources for the LVMVolumeGroup ones.

3. Added spec.local field.
   This field includes only one subfield nodeName, which stores the information about the node the resource is placed on.

What is the expected result?

1. lvmvolumegroups CRD and CRs have LVMVolumeGroup kind
2. Old-kind LvmVolumeGroup resources are migrated to new-kind LVMVolumeGroup ones (they have Ready state, the information in them is correct, and their spec.blockDeviceNames are stored as spec.blockDeviceSelector.

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.