Improve kubeone reset output

[xmudrii]

What this PR does / why we need it:

The kubeone reset output currently looks like this:

WARN[16:53:00 CEST] this command will require an explicit confirmation starting with the next minor release (v1.3) 
The following nodes will be reset. The Kubernetes cluster running on those nodes will be permanently destroyed 
	- reset control plane node "marko-1-cp-0" (10.0.42.9)
	- reset control plane node "marko-1-cp-1" (10.0.42.14)
	- reset control plane node "marko-1-cp-2" (10.0.42.5)
INFO[16:53:00 CEST] Building Kubernetes clientset...             
	- reset machine-controller managed machine "marko-1-pool1-57494466fb-rsx4b"

There are several issues with the output:

• the Building Kubernetes clientset... is in between a list of control plane nodes and Machines, which doesn't look nice
• reset machine-controller managed machine is wrong in this context because the Machine is actually destroyed
• the warning is outdated because the command already requires an explicit confirmation
• the Kubernetes clientset will be built again after confirming the command which is not needed at all

This PR is supposed to fix those issues and add some additional context to the output. With this PR, the output looks like this:

INFO[18:25:44 CEST] Building Kubernetes clientset...             
WARN[18:25:50 CEST] This command will PERMANENTLY destroy the Kubernetes cluster running on the following nodes: 
	- reset control plane node "marko-1-cp-0" (10.0.42.3)
	- reset control plane node "marko-1-cp-1" (10.0.42.8)
	- reset control plane node "marko-1-cp-2" (10.0.42.14)

The following machine-controller managed worker nodes will be destroyed:
	- kube-system/marko-1-pool1-5df867f674-vp8kg

After the command is complete, there's NO way to recover the cluster or its data! 
Do you want to proceed (yes/no): yes

INFO[18:25:54 CEST] Destroying worker nodes...                   
INFO[18:25:55 CEST] Annotating nodes to skip eviction...         
INFO[18:25:56 CEST] Deleting MachineDeployment objects...   
...

Does this PR introduce a user-facing change?:

NONE

/assign @kron4eg

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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 [xmudrii]

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

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 2d2f3383ca33811f1b26061d26f4d1b8374bf0e5