TBI - no middleware specific knowledge and type definitions in @sap-ux/ui5-config

[heimwege]

Description (include screenshots)

@sap-ux/ui5-config should provide a comfortable way to work with ui5.yaml files without having knowledge and type definition for all middlewares there. The type definition of a middleware belongs to the respective middleware. Module @sap-ux/ui5-config should be able to work with generics meaning, consumers bring their own type.

Value

Currently to support a new setting you need to update two modules. With this TBI changing or just adding a setting for a middleware no longer requires changing the type in @sap-ux/ui5-config.

Architecture Elaboration

Does it requires architecture elaboration? Yes

Notes

@Klaus-Keller @tobiasqueck

Tasks

• Move existing middleware specific types from ui5-config to the respective middleware
• Move existing middleware specific functions from ui5-config to the respective middleware

[Klaus-Keller]

Thanks @heimwege, this change makes sense to me and helps decoupling different modules and responsibilities. No objections.