Batch delete workspaces with `--orphan`

[aslilac]

Some quick thoughts around this:

• We've restricted the ability to orphan delete in the UI to workspaces which have failed to build, because you'll almost never want to leave dangling resources, and should just do a regular delete if you're at all able. We should preserve this behavior in batch delete: do not allow orphaning healthy workspaces.

• We could provide an orphan option checkbox next to each workspace on the batch delete review page, which would require you to individually select each workspace that will be left with orphaned resources.

  • I'm not sure exactly how we would communicate the danger of orphaning in this setup without getting to cluttered.

• We could only show the orphan option if every workspace in the list is failed.

• We could provide a "smart" orphan option if any workspace is failed, that will only orphan delete workspaces which are failed, and will delete other selected workspaces the normal way.

  • One drawback to this is the ambiguity of which workspaces will be left with orphaned resources, that will need to be cleaned up manually.

• The resources review page in the batch delete flow could make it very clear exactly what resources will be left orphaned.

  • Maybe provide a complete list of orphaned resource names and types that can easily be copied and pasted.

[bpmct]

I kind of like the smart orphan option. Alternatively, we could link to documentation that has a CLI script to bulk orphan if (if any of workspaces are in failed state) if we think that is safer.