Migrate infrastructure related logic + configuration from KEB to KIM

[tobiscr]

Description

A goal of the KIm is to establish a domain for infrastructure relate tasks (primarily cluster creation) within Kyma. At the moment is KEB heavily involved in this area as managing several decisions about the cluster creation (e.g. which region has to be used etc.).

To establish KEB as pure orchestration service for Kyma backends, all infrastructure related logic in KEB should be extracted and become part of KIM.

AC:

• Get in contact with KEB team and
  • verify the different steps applied by KEB during the cluster creation process
  • decide together which logic should be removed from KEB an integrated into KIM
• Extract infrastructure related logic from KEB and integrate it into KIM
  • Identify scope of the migration (define work packages, identify features)
  • Agree on the migration strategy (avoid a big-bang migration, make it "gruanlar" to migrate things step by step)

Depends on
#125 + #134

Relates to
#600

[Disper]

As part of the migration, please do not forget about planning the removal of https://github.com/kyma-project/control-plane/tree/main/components/schema-migrator.

[Disper]

This PR should be done before we finalise KIM migration.

[Disper]

We have to double check with Gophers if we have not missed anything.

[tobiscr]

@piotrmiskiewicz / @PK85 / @ebensom - JFYI: this is the issue we will use to migrate configuration parameters which are pure infrastructure related from KEB to KIM.

WE also agreed that SRE will switch to server-side-apply and take over the the field-ownership of these values which are usually only relevant for them (e.g. infrastructureConfig + controlPlaneConfig).