Don't enable kubelet until after kubeadm generates config

[priyawadhwa]

As written in the k8s 1.19 CHANGELOG:

Kubeadm: Move the "kubeadm init" phase "kubelet-start" later in the init workflow, after the "kubeconfig" phase. This makes kubeadm start the kubelet only after the KubeletConfiguration component config file (/var/lib/kubelet/config.yaml) is generated and solves a problem where init systems like OpenRC cannot crashloop the kubelet service. (#90892, @xphoniex) [SIG Cluster Lifecycle]

Starting kubelet before the config exists caused up to 3x longer start time with 1.19. This PR removes the call to start kubelet before kubeadm init, and also puts the kubeadm phases in the correct order.

fixes #9106

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: priyawadhwa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [priyawadhwa]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[priyawadhwa]

/ok-to-test

[minikube-pr-bot]

kvm2 Driver
error collecting results for kvm2 driver: timing run 0 with Minikube (PR 9111): timing cmd: [/home/performance-monitor/.minikube/minikube-binaries/9111/minikube start --driver=kvm2]: starting cmd: fork/exec /home/performance-monitor/.minikube/minikube-binaries/9111/minikube: exec format error
docker Driver
error collecting results for docker driver: timing run 0 with Minikube (PR 9111): timing cmd: [/home/performance-monitor/.minikube/minikube-binaries/9111/minikube start --driver=docker]: starting cmd: fork/exec /home/performance-monitor/.minikube/minikube-binaries/9111/minikube: exec format error