[controller] Enhance LVMLogicalVolume handling: logging, size display, and event processing

[AleksZimin]

Description

This PR introduces several improvements to controller managing LVMLogicalVolume. Key enhancements include field organization, improved logging mechanisms, and an update in how actualSize is displayed to present a human-readable format. Additionally, the update function's event processing in the watcher has been refined to trigger only upon changes in the LVMLogicalVolume spec. The method for checking the actual size of LVs on nodes has also been optimized to query specific LVs rather than all LVs on the node, increasing efficiency and accuracy. Furthermore, LV search functionality now accounts for Volume Groups (VGs), ensuring more precise operations.

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

These changes streamline controller operations and enhance user and system interaction by:

• Improving the clarity and usefulness of logs.
• Making size information more accessible and understandable for users.
• Reducing unnecessary event processing, enhancing system performance.
• Improving LV size checks and search functionality for better accuracy and efficiency.

What is the expected result?

• Users and administrators will benefit from more informative and readable logs.
• The actualSize field will now display in a user-friendly format, improving interface usability.
• Event processing optimization will lead to reduced system load.
• Enhanced LV size checking and search accuracy will ensure more reliable and efficient storage management.

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.