KIM Integration - redesign configuration after migration is done

[jaroslaw-pieszka]

When we use KIM only, provisioner is no longer used, we need to simplify and unify configuration.

To many steps we pass separately input.Config and broker.KimConfig objects.

AC:

• we pass one configuration object to all steps that need it
• there are no longer provisioner related settings (this is in scope of different ticket)
• KIM migration related settings are removed
• some previously used settings become KIM related and possible should be moved to kim section

[jaroslaw-pieszka]

Blocked till migration is done.

[jaroslaw-pieszka]

Following configuration values should be migrated to kim section (are used to create Runtime CRs`:

• Provisioner.KubernetesVersion
• Provisioner.DefaultGardenerShootPurpose
• Provisioner.MachineImage
• Provisioner.MachineImageVersion
• Provisioner.DefaultTrialProvider
• Provisioner.MultiZoneCluster
• Provisioner.ControlPlaneFailureTolerance

We could consider moving:

• Broker.UseSmallerMachineTypes to kim section

Following values should be moved to other place (possible section with timeouts - there are more timeouts settings scattered):

• Provisioner.ProvisioningTimeout
• Provisioner.DeprovisioningTimeout
• Provisioner.RuntimeResourceStepTimeout
• Provisioner.ClusterUpdateStepTimeout

Following values should be removed (double check before actual removal):

• Provisioner.URL
• Provisioner.TrialNodesNumber
• Provisioner.AutoUpdateKubernetesVersion
• Provisioner.AutoUpdateMachineImageVersion
• Provisioner.EnableShootAndSeedSameRegion

Removal is blocked until provisioner is decommissioned and only KIM is driving/controlling the process.

[jaroslaw-pieszka]

This is blocked by #1187 and #1298