Add JSON output to minikube delete

[spowelljr]

Closes #13961

1. Added -o or --output flag to minikube delete
2. Removed duplicate Deleting register step from Deleting action
3. Add Purging register step to Deleting action
4. Changed repeat steps from Step to Styled

$ minikube delete --all --purge -o json
{"specversion":"1.0","id":"2d0d5bff-5a3b-4958-a0f8-3da6d4a2cefb","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.info","datacontenttype":"application/json","data":{"message":"Removed all traces of the \"minikube\" cluster."}}
{"specversion":"1.0","id":"c1c41195-092d-47d6-a089-5771b87e2f82","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"2","message":"Successfully deleted all profiles","name":"Done","totalsteps":"3"}}
{"specversion":"1.0","id":"f6f04a5e-1d22-446d-8199-9ddb81b9c355","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"3","message":"Successfully purged minikube directory located at - [/Users/powellsteven/.minikube]","name":"Puring home dir","totalsteps":"3"}}

Why was Step replaced to Styled?
Steps are supposed to be distinct, the problem arises with delete --all. Multiple profiles may be deleted with a single command, causing duplicates of the same step to be logged.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spowelljr

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

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

[medyagh]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 13979) |
+----------------+----------+---------------------+
| minikube start | 51.1s    | 50.6s               |
| enable ingress | 29.6s    | 29.5s               |
+----------------+----------+---------------------+

Times for minikube start: 51.7s 51.1s 51.1s 49.8s 51.7s
Times for minikube (PR 13979) start: 50.8s 49.3s 50.4s 51.8s 51.0s

Times for minikube ingress: 29.5s 30.0s 30.5s 29.6s 28.5s
Times for minikube (PR 13979) ingress: 29.5s 30.0s 29.6s 30.0s 28.5s

docker driver with docker runtime
error collecting results for docker driver: timing run 0 with minikube: timing cmd: [out/minikube addons enable ingress]: waiting for minikube: exit status 10
docker driver with containerd runtime
error collecting results for docker driver: timing run 0 with minikube: timing cmd: [out/minikube addons enable ingress]: waiting for minikube: exit status 10