MS-1058 Implementation of signed url sample upload

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Notable changes

• Changed the image repository interface to accommodate for the extra information required for sample upload with signed URLs.
• Moved sample file path creation into the module to ensure consistent paths and have an option to break that path back into usable metadata about the sample (session ID, modality and sample ID).
• Refactored the existing Firestore image uploader out of the ImageRepositoryImpl to allow for different approaches to reading files from the disk:
  • Firestore - reads and uploads files one by one in sequence until all are uploaded.
  • Signed URL - reads files in batches to calculate size and MD5 values, requests the upload URLs for the whole batch with a request, then proceeds to upload files one by one within the batch until all batches are uploaded.
• Important - encrypted file input stream that we are getting from the local disc can only be read once and cannot be reset, therefore any BODY-level network logging (both chucker and okhttp) will consume the stream to print it out, and the actual file upload will fail.

Testing guidance

• Enable sample/image upload in Vulcan.
• Do several biometric flows with face or fingerprint tracking sessions IDs. Wait a couple of hours until the state in sync info screen shows that images were uploaded. Check Firestore for the uploaded images by project and session IDs.
• Enable signed URL upload with custom configuration.
• Do several biometric flows with face or fingerprint tracking sessions IDs. Wait a couple of hours until the state in sync info screen shows that images were uploaded. Check the new sample storage for the uploaded images by project and session IDs.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[luhmirin-s]

@alexandr-simprints I have added more general logging around the upload to help us restore the timeline in crash logs (if it will be necessary). There isn't much else we could add to those logs, tho.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud