[FEATURE] KymaEnvironment returns kubeconfig to allow orchestration in fully automated way

[JohannesRu]

What happened?

CloudOrcehstrator outlined how orchestrated Gardener Shoots can be automatically filled with workload content.
https://pages.github.tools.sap/cloud-orchestration/docs/use-cases/workload_to_shoot

this ease is asked for Kyma scenario. Until today, this was a rather complex approach incl. manual steps
https://pages.github.tools.sap/cloud-orchestration/docs/use-cases/workload_to_kyma

This process can be simplified not as Kyma provides the necessary OIDC capabilities.

As i understand reading https://help.sap.com/docs/btp/sap-business-technology-platform/managing-kyma-runtime-using-provisioning-service-api, you are now able to request a kubeconfig to your BTP Kyma cluster, but the time to live (TTL) is short.
In conclusion, this kubeconfig needs to be requested automatically and periodically for a MCP to have access to the BTP Kyma cluster.
Just like kind: AdminKubeconfigRequest from Gardener (https://pages.github.tools.sap/cloud-orchestration/docs/use-cases/workload_to_shoot#gardener-auth-provider) but for Kyma.

What you expected to happen?

• Update end user guide to consider new Kyma capabilities for simpler orchestration
• Bring this into the BTP Provider?
• Create requried Providers - if necessary - KymaAuthProvider?