Rudoi/honor machinedeployments in machine phase

[rudoi]

What this PR does / why we need it:

The apply-machines phase will now detect and apply MachineDeployments as nodes, and therefore, so will clusterctl create cluster.

Release note:

Support MachineDeployments as part of the apply-machines phase

[h0tbird]

Be aware that CAPA requires a change too to be compatible with this code.
https://github.com/newrelic-forks/cluster-api-provider-aws/blob/6f304f5e2d2c51e16d608797bba790e0306b4787/pkg/cloud/aws/services/kubeadm/aws_defaults.go#L169

➜  cluster-api-provider-aws git:(test-andrew-pr) ✗ git diff
diff --git a/pkg/cloud/aws/services/kubeadm/aws_defaults.go b/pkg/cloud/aws/services/kubeadm/aws_defaults.go
index 9721c874..34da098d 100644
--- a/pkg/cloud/aws/services/kubeadm/aws_defaults.go
+++ b/pkg/cloud/aws/services/kubeadm/aws_defaults.go
@@ -166,7 +166,7 @@ func SetJoinNodeConfigurationOverrides(caCertHash, bootstrapToken string, machin
                klog.Infof("Overriding node's cloud-provider to the required value of %q.", cloudProvider)
        }
        base.NodeRegistration.KubeletExtraArgs["cloud-provider"] = cloudProvider
-       if !util.IsControlPlaneMachine(machine.Machine) {
+       if !util.IsControlPlaneMachine(machine.Machine.Spec) {
                base.NodeRegistration.KubeletExtraArgs["node-labels"] = nodeRole
        }
 }

[rudoi]

@h0tbird I created a new function specific to MachineDeployments as to not break that function.

[h0tbird]

One typo

[h0tbird]

A MachineDeployment cannot be used to coordinate the init and join phases.
I think we should be able to use a MachineDeployment for all the join nodes after the pivot takes place.

[h0tbird]

LGTM