Restructure file system

[yuanchen233]

Currently the file system accepting file upload and storage it under carp/storage, we should create a subfolder for each study and storage related resources under this study-subfolder. Once a study is deleted, the corresponding folder and resources should also be deleted.

and also for s3?

[bardram]

Remember to check the download / export scripts when changing the file structure.

[pavliuc75]

What we change?
-how we save export (depl/study)
-change the controller
-change to db (ownerId, deploymentId, studyId)

[pavliuc75]

Database changes:

DELETE FROM public.files;
DELETE FROM public.exports;

ALTER TABLE public.files
ADD COLUMN owner_id VARCHAR(255),
ADD COLUMN deployment_id VARCHAR(255),
ADD COLUMN relative_path VARCHAR(1000),
RENAME COLUMN storage_name TO file_name;

ALTER TABLE public.exports
ADD COLUMN relative_path VARCHAR(1000);

File system new structure:
When uploading a file:
.../studies/1234/deployments/5678/{newFile.jpg}
When generating an export for a deployment:
.../studies/1234/deployments/5678/exports/{theExport.zip}
When generating an export for the entire study:
.../studies/1234/exports/{theExport.zip}

RestAPI changes in FileController:

• the create ("/api/studies/{{STUDY_ID}}/files") is renamed to createDEPRECATED
• a new endpoint is added -> create ("/api/studies/{{STUDY_ID}}/files/{{DEPLOYMENT_ID}}")

Caveats:
since some clients will still be using the createDEPRECATED endpoint, there is no way we can know the deploymentId when saving to database. If that's the case, the deploymentId for that row in db will be null, while the file will be saved with the relative path e.g. .../studies/1234/deployments/unknown/{newFile.jpg}. When generating an export for the entire study, we include the files from the unknown folder.