Remove non-VO dirs from data retention policy

[hajgato]

In the old system, user had to sign a document and it was clear all data (including non-VO VSC_HOME, VSC_SCRATCH, VSC_DATA, VSC_ARCANINE_SCRATCH) would go to the new data owner. In the new system we do not have this clearly formulated, so I would leave the non-VO locations as it is (VSC_HOME can contain sensitive information like ssh-private-keys, etc).
Moreover, if users were member of multiple VOs, its not easy to determine (without the explicit request of the user), to which VO should ve transfer the non-VO directories. In general, the leftover data of non-VO location is very small, so it would not cause any storage space problems.
We also write that promotors can get the data, but how we can check that? What if the promotor does not have a vsc account?

[epauwels]

Okay for me.
So, 'personal' VSC_DATA and VSC_HOME directories are off-limits basically.

The promotor passage is there to enable it 'in theory'.
In practice this will obviously not be that simple.
Checking can be done (on our end) by contacting DPO I guess.
But I imagine the transfer would be by request from the promotor then (who should, indeed, then make a vsc-id etc. etc.)