feat: pass document dates in applications & registrations responses

[JazzarKarim]

Issue:

• API - Pass Documents Date to Applications & Registrations entity#32298

Description of changes:
Registrations endpoint, before:

After:

Applications endpoint, before:

After:

The fix for registrations was very simple, just grab the created date from the documents table if addedOn is not found.

The fix for applications was trickier though as we don't store documents in the documents table if there is no registration yet. I created a function that grabs the date from GCP storage.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the BC Registry and Digital Services BSD 3-Clause License

[dimak1]

@JazzarKarim what about uploadDate, should it be also in the picture somewhere?

[JazzarKarim]

@JazzarKarim what about uploadDate, should it be also in the picture somewhere?

No, the uploadDate is just an internal field we'll use sometimes to fill the addedOn field. For the UI, the addedOn field is what we'll be using (you can ignore that uploadDate field).

[dimak1]

@JazzarKarim during document upload during application, we do use uploadDate in BaseUploadAdditionalDocuments.

[thorwolpert]

nice addition!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud