Deleting a CO or provisioner does not deprovision the data

When a CO is deleted, or only a related provisioner, the associated data is not deprovisioned properly, causing the target system to retain the information.

If at a later stage a similarly named CO is created, the original data may still be present. This can cause at the very least a jumble of mixed information, but may lead to parties getting access to data they should not have access to.

The expected behaviour would be for deleted provisioners to be called for each provisionable item to delete that item. Alternatively, a special 'deprovision all' action could be implemented to allow the provisioner to easily delete an entire structure.