Provide Default Views for CRDs and Other Objects

[finally-fancy]

Description
Instead of relying solely on the YAML editor when a UI definition is not provided by the CRD owner, Busula can automatically generate a generic UI based on the CRD's schema, leveraging the CRD's metadata or the OpenAPI 3.0 specification. This would provide a visual, structured interface for users to interact with CRDs even if no custom UI is provided by the CRD provider.

Reasons
Currently, in Busula, if the CRD provider does not supply a UI definition for a Custom Resource Definition (CRD), the user is limited to interacting with that resource through a YAML editor. While this allows for flexibility, it is far from user-friendly, especially when dealing with a high number of CRDs or when non-technical users need to interact with these resources. As service providers continue to introduce more CRDs, managing and interacting with them via raw YAML becomes inefficient and unscalable.

This issue becomes more pronounced when dealing with uncontrolled provisioning of services by partners. If hundreds or even thousands of CRDs are introduced without a proper UI for each, users are forced to edit raw YAML, which increases the potential for errors and slows down operations. Moreover, the lack of a visual, intuitive interface hinders the user experience, making it difficult for teams to manage resources at scale.