miniziti on macOS and Windows gets connection refused

[qrkourier]

This happens when the minikube tunnel is still running from a prior miniziti cluster because minikube tunnel fails forever when the cluster disappears, and miniziti.bash only checks to see if it's running, not whether it's healthy.

An alternative is to start managing the minikube tunnel process inside miniziti.bash.

[qrkourier]

This is a pain point on Linux too, for the record. It only seems to recur when resuming a miniziti instance. I'm guessing one additional status conditional is necessary, and managing the tunnel process makes a whole lot of sense, especially for macOS and Windows where there's always an extra step if the user doesn't happen to know that's necessary in advance.

[qrkourier]

@sabedevops Please branch from this ref in miniziti's new home: #1324

[qrkourier]

miniziti.bash was improved to only restart the cluster if not ready.