Improve message when selected driver is incompatible with existing cluster

[tstromberg]

Before:

😄  minikube v1.5.2 on Debian rodete
💥  The existing "minikube" VM that was created using the "kvm2" driver, and is incompatible with the "none" driver.
👉  To proceed, either:
      1) Delete the existing VM using: 'minikube delete'
      or
      2) Restart with the existing driver: 'minikube start --vm-driver=kvm2'

After:

😄  minikube v1.5.2 on Debian rodete
💥  The existing "minikube" cluster was created using the "kvm2" driver, and cannot be started using the "none" driver.
👉  To proceed, either:

    1) Delete the existing "minikube" cluster using: 'minikube delete'

    * or *

    2) Start the existing "minikube" cluster using: 'minikube start --vm-driver=kvm2'
	
💣  Exiting.

I believe the previous message may have been confusing to users, based on the context in #5828

/cc @a1exus

[k8s-ci-robot]

@tstromberg: GitHub didn't allow me to request PR reviews from the following users: a1exus.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Before:

😄  minikube v1.5.2 on Debian rodete
💥  The existing "minikube" VM that was created using the "kvm2" driver, and is incompatible with the "none" driver.
👉  To proceed, either:
     1) Delete the existing VM using: 'minikube delete'
     or
     2) Restart with the existing driver: 'minikube start --vm-driver=kvm2'

After:

😄  minikube v1.5.2 on Debian rodete
💥  The existing "minikube" cluster that was created using the "kvm2" driver, and cannot be started using the "none" driver.
👉  To proceed, either:

   1) Delete the existing "minikube" cluster using: 'minikube delete'

   * or *

   2) Start the existing "minikube" cluster using: 'minikube start --vm-driver=kvm2'
  
💣  Exiting.

I believe the previous message may have been confusing to users, based on the context in #5828

/cc @a1exus

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tstromberg

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

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

[tstromberg]

/ok-to-test

[codecov-io]

Codecov Report

Merging #5854 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5854      +/-   ##
==========================================
- Coverage   36.53%   36.52%   -0.01%     
==========================================
  Files         110      110              
  Lines        8116     8117       +1     
==========================================
  Hits         2965     2965              
- Misses       4762     4763       +1     
  Partials      389      389

Impacted Files	Coverage Δ
cmd/minikube/cmd/start.go	19.97% <0%> (-0.03%)	⬇️

[minikube-bot]

Error: running mkcmp: exit status 1

[medyagh]

I like the new format and space between lines. We need. More of this easy to read solution message