change core-service to use PVCs per-project/per-user #3008
Description
To support scalability, we need a way to have PVCs added dynamically to core service on a per-user (or per project) level, which can be re-used in delayed jobs.
These PVCs should be added when a user first tries to access the project. The project should then be cloned into them in a pre-determined path (analogous to /svc/cache/... we have now).
Check how they could be provisioned and managed.
We probably still need to track them in redis so we know what is there.
If a PVC already exists, it should be mounted/reused. If it is already mounted, we should use it directly (maybe with a regular pull as we have it now).
For the uploaded file cache, we probably also want a dedicated PVC storing the files. If we have PVCs per user, we could also opt to store them there.