🔨 enh: capd workloadcluster prov. with argocd workflow trigger

[PatrickLaabs]

/kind feature

Describe the solution you'd like
When we create a workload cluster ontop of the mgmt cluster, the workload cluster has to pull a lot of things in order to get fully ready.
As soon, as the control plane is ready - on mgmt-clusters perspective - the argocd workflow kicks in, and tries to run every thing.
The Script will fail, since the worker nodes and everything else is not yet fully ready and the part "Adding the workload cluster to argohub" will not work.

As a workaround, i set a high timer, so that the script will wait till everything will - eventually - be up and running.

Best solution would be:
Checking, that everything is up and running on the workload cluster. Maybe we should think about an event type, or using cloud events.

Anything else you would like to add:
This might be only an issue on local development, and might depend on your actual download speed from your internet provider.

[PatrickLaabs]

With PR #74 I introduced the statuscheck package, which allows us to check for deployment states of whatever deployment you like.

With this package, we could implement a check to make sure, that everything is up and running, before we allow the script to run.

Whats happening:

• a workload cluster is prov. against the mgmt cluster
• the workload cluster will become almost immediately ready
• the workload cluster installs everything needed via helmchartproxies
• the script will start to run, as soon as the workload clusters state is ready (which is almost directly after provisioning.)