[Postgres] CONSTRAINT unique_ingested only looks at the submission_file_path and the archive_file_path

[jbygdell]

Describe the bug

Since we prefer not to leak the submitter ID from the file path of the uploaded file we need to make sure that the constraint in the SQL schema doesn't only look at the submission file path and whether or not the file has been ingested already before giving it an ID.

Related to #1097

Steps to reproduce

Start the postgres container in any way you like.
Exec into the container and run the following queries.

SELECT sda.register_file('path/to/testfile.ex', 'testuser');
SELECT sda.register_file('path/to/testfile.ex', 'another-user');

You will see that the returned IDs are identical since the CONSTRAINT unique_ingested only looks at the submission_file_path and the archive_file_path

Expected behavior

• Multiple users should be able to submit files with the exact same file path at the same time.
• A user should be able to submit files with the same name several times, given that the previous file has been ingested.
• Tests verifying the fix are added

Additional context

Estimation of size

small

Estimation of priority

low