Automate Redfish OpenAPI Tooling Move & CI/CD Integration for OpenAPI Autogeneration

[sudhir-intc]

Is your feature request related to a problem? Please describe.

There is a need to modularize and automate the handling of Redfish OpenAPI tooling by:

• Moving all Redfish OpenAPI tooling (python scripts, yaml files) present in https://github.com/nmgaston/console/tree/main/redfish/openapi into a new dedicated repository to streamline maintainability and separation of concerns.
• Establishing automated CI/CD workflows to keep the main console repository (@device-management-toolkit/console) updated with the latest OpenAPI specifications and related autogenerated code.

Describe the solution you'd like

• Relocate all Redfish OpenAPI tooling (including Python scripts for code generation, YAML spec files, etc.) from current location to a newly created dedicated repository under the device-management-toolkit org.
• Set up robust CI/CD pipelines in the tooling repository that, on updates to OpenAPI artifacts, automatically create a pull request (PR) targeting the @device-management-toolkit/console repo, delivering both the updated OpenAPI file and the newly autogenerated code (client/server stubs or relevant bindings).

Describe alternatives you've considered

• Manual updates to the console repo when OpenAPI specs/tooling change (less efficient, risk of inconsistencies, more error-prone).
• Keeping tooling within the console repo (reduces modularity and complicates codebase).

Additional context

• This feature must ensure that release engineering and integration of Redfish support remain consistent and automated as both the OpenAPI schema and generated outputs evolve.
• Collaboration might be needed between maintainers of both the tooling and console repos to finalize permissions and integration flows.
• This is tightly coupled with ongoing Redfish management integration efforts.
• This issue is related to Integrate Redfish Management (Power & Inventory) in DMT Console #782.