EUCA-9296 Workaround to ensure that if BFEBS instances fail to execute, the user is able to
access and delete the underlying root volumes.

1. If the SC does not report a volume, it will be transitioned to an "error" state.
2. If a BFEBS run fails, the CLC will continue to report the volume (although in an "attached") state.
The workaround is to call terminate on the instance(s) again, at which point the volume can be
deleted using the API.

Conflicts:
	clc/modules/cluster-manager/src/main/java/com/eucalyptus/cloud/run/ClusterAllocator.java
EUCA-9296 add timeout before transitioning vol to ERROR.
Ensure volume metadata is not rolled back on run failure - EUCA-9296

Conflicts:
	clc/modules/cluster-manager/src/main/java/com/eucalyptus/cloud/run/ClusterAllocator.java
EUCA-9501 Delete vol on SC should be idempotent if vol not found.