POC service and worker cluster

[Kidswiss]

Summary

Implementing control and worker cluster support needs following considerations:

• Managing multiple kubeconfigs for provider-helm and provider-kubernetes
• Validation webhooks will need access to the controlcluster
• We can't keep using connectionDetails like we currently do
  • They can't be written to the worker cluster directly, so they need to be deployed via provider-kubernetes
  • Some helper functions to automatically deploy the the connectiondetails of a given resource via provider-kubernetes would be helpful
• It's very important to strictly differentiate between managed resources and plain kubernetes objects
  • Unfortunately there are managed objects that don't implement the resource.Managed interface in go, so making the compiler help us with this might be hard
  • ProviderConfigs and Usages are such objects, their golang types don't implement the necessary interface, but they should not be wrapped into kube objects
  • We need to build logic in the runtime to make this as seamless as possible, so that it automatically decides if it's a managed resource or not
    • We might want to get rid of the API that differentiates between those two types and hide it behind a generic function
    • As managed resources are always cluster scoped, it should be possible to detect if any given object should be wrapped or not

Checklist

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• Update tests.
• Link this PR to related issues.