UI Layout and Extension Configuration Validation

[finally-fancy]

Description
A better approach would be to introduce a Custom Resource Definition (CRD) to represent the UI layout and configuration. This solution would improve the validation process, centralize configuration management, and provide more control over how the UI extensions are defined and maintained.

Reasons
Current Implementation: Busula stores the configuration for UI layout and extensions in ConfigMaps within the Kubernetes cluster. These ConfigMaps hold the structure and configuration of the UI, including settings for extensions that customize the Busula dashboard. Essentially, the ConfigMap contains YAML data that outlines how the UI should behave, how different elements are structured, and how extensions (such as additional buttons, panels, or sections) are integrated.

Since the ConfigMap is a simple Kubernetes object with a string-based structure, there’s no validation when the ConfigMap is applied during the deployment. Any errors in the YAML configuration are only detected during runtime when the frontend attempts to load and interpret the configuration. This means that issues like syntax errors, incorrect references, or structural problems in the UI config only become apparent when users interact with the dashboard, leading to runtime failures.