./start cleanup deletes PersistentVolumes which are valid, but not bound

[Stono]

At the moment, the cleanup script is detecting PersistentVolumes as part of PersistentVolumeClaims that are not bound, but still valid.

For example; take a StatefuleSet with a PVC Template, scale it to 3, then down to 2, and you'll still have 3 disks (valid), clenaup will delete that third disk, leaving the PVC in an invalid state.

PV's should be checked against PVC's, not just for their bound status.