When an island setup deployment fails, the associated volumes are automatically deleted

[g-crocker]

Describe the bug

For example, when we run nha -d -p isle mongo setup and for any reason the deployment fails, Noronha will automatically revert the creation of associated volumes (in K8s, PVCs), even if those volumes were already there before the command was run.

This can be a major issue if someone already has isles running in their cluster and need to reconfigure them (e.g.: update the resource profile), if for some reason the setup command fails, Noronha will remove existing PVCs without even prompting the user, completely erasing it's own database.

Expected behavior

1. Noronha should prompt the user if this action should be done
2. The default option should be to leave the volumes there