style: address flake8 e402 warning in the codebase

[Sharansrj567]

Initiated the resolution of Flake8 E402 warnings throughout the codebase by moving imports to the top of the files. However, encountered a scenario where certain module imports are conditional based on the platform (Windows or non-Windows).

Due to platform-dependent imports, moving them to the top would break the conditional logic. To maintain code integrity and adhere to PEP 8, introduced a pattern where platform-specific imports are encapsulated within functions, ensuring they are called when needed.

Following this adjustment, successfully resolved E402 warnings associated with conditional imports.

Subsequently, addressed E302 and E305 warnings by adding appropriate blank lines after import statements and before class/function definitions. This conforms to PEP 8 conventions for improved code readability.

The codebase now aligns with coding standards, maintains platform-specific imports efficiently, and has an enhanced overall structure.

Related to: issue #1522