Improve resource cleanup

When a cluster creation fails, the process of cleaning up resources is manual, cumbersome and prone to errors
We could automate most of this to improve user experience when debugging.
We already have a `--force-cleanup` flag, it just doesn't do a lot. Think about everything you need to do when a cluster creation fails before running the cli again, that's what we should try to add to this flow. Examples:
* Delete bootstrap cluster. We do that today, but it's not super robust. Find when it doesn't work and fix it.
* If we don't support more than one kind cluster running, even if it's not an eks-a one, add a validation for this and give instructions to delete them
* Cleanup vsphere vms if it's a vsphere cluster
* Cleanup docker resources if it's a docker cluster
* Delete `` folder

Locate the --force-cleanup flag and its existing bootstrap-cluster cleanup path first. Trace what happens after cluster creation fails, then compare that flow with the listed Docker, vSphere, kind, and cluster-directory cleanup cases. Done means the supported cleanup actions are automated where possible, existing failures are handled robustly, and unsupported running clusters produce clear deletion instructions.

Written by the indexing model from the issue text.