Make UI `ManagedControlPlanev2` ready

[GenosseOtt]

Description

As we offer ManagedControlplanev2 next to ManagedControlPlane, we want to support both via UI!

We want to encourage usage of the newer version and mark existing control planes as deprecated.

Tasks

Onboarding API

• Introduce Feature Toggle

• Mark ManagedControlplanes as deprecated

  • On ManagedControlPlane card in workspace
  • On ManagedControlPlane detail page header
  • ManagedControlplane can be edited
  • ManagedControlplane can be deleted
  • ManagedControlplane cannot be create
  • ManagedControlplaneV2 can be create

• On creation only allow creation of ManagedControlplaneV2

  • Ensure Services can be installed
  • Ensure Members (Users/ServiceAcounts) can be added/deleted/edited as today

• ManagedControlplaneV2 can be edited

• ManagedControlplaneV2 can be deleted

Note: Today, Crossplane and Landscaper can be installed - therefore installing them is in scope. All other ServiceProvicers are streteched goal

Connect ManagedControlPlane v2

• Until PlatformService is written - use backend proxy

• Backend Proxy: Enrich support for ManagedControlPlanev2

• End users can connect to ManagedControlPlanev2 instances

• Kubeconfig can be downloaded

• Crossplane managed resources are shown (/managed will work as usual)

• Installed Services are visible

• Custom Identity Providers are sill supported

• Resources can be created/edited/deletes as before

• GitHub client still works

Related

• We proof this development on regular Development landscape
• Please create/reuse a Project for entire webapp team plus core friends

Scope

• Support for ManagedControlplane and ManagedControlplaneV2
• ManagedControlplaneV2 is behind a Feature Toggle
• Deprecate ManagedControlplane

Out of scope

• Additional features introdcued by ManagedControlplaneV2 offering
• GraphQL changes are tracked seperately - please link Onboarding API & ManagedControlPlane one - @andreaskienle
• PlatformService