failed kurtosis-engine deployment is not recognised as such

[0x416e746f6e]

What's your CLI version?

1.4.3

Description & steps to reproduce

If kurtosis cluster set command fails for whatever reason, the "failed" cluster id is nevertheless remembered, and any consequent attempt to re-run the command will simply say that the desired cluster is already set.

For workaround, one has to use kurtosis cluster set to set the cluster to something else (e.g. to docker), and then re-run the original command again.

Desired behavior

Mark new cluster as "set" only when all the operations were successful.

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

CLI: the Command Line Interface