Allow customization of deployed Webapp Stack

[GenosseOtt]

Description

As an adminstrator of openMCP, I may or may not want to have certain features or views enabled in my openMCP UI.
The UI code should be completly agnostic to that and solely rely on a Config file, hosted on the Onboarding API.

In this issue we collect possible feature flags for end users to enable/disable

Onboarding Configurations

• Usage analytics: Dynatrace or other
• Enforce "One MCP view", users cannot create additional Projects, Workspaces, MCPs, skip navigation around

Managed Control Plane settings

• Preconfigured Views
• Hide deletion
• Refernce custom Platform/End user guides

[n3rdc4ptn]

We could put in a hand written CRD into our UI which the UI installs using a ServiceAccount is gets when deployed. A ProviderConfig like a PlatformService. The UI could then reconcile it in the Backend and provide the configuration via an endpoint or injecting it.

So in simple words, it would be a javascript based Kubernetes operator.