Comment 3 for bug 1843331

It seems like it should better handle the case where the cluster is no longer reachable for whatever reason. Even when using `juju destroy-model --force --no-wait k8s-model`, it just hangs there pretty much indefinitely, since I guess it's waiting for each individual operation to timeout? Maybe at the start of the model destruction, it could do a basic connectivity test and, especially if it's already been given `--force`, just skip trying to do the individual operations.