Document Record Service Continuation In Integration

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-07-29. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjEwODI1)._

As a Registries Analyst, I want to be able to work from the top of the new Queue service and have the digital artifacts already available for the filing.

Applicants should be able to provide supporting documentation which will be stored in the new Document Record Service, replacing MinIO as the repository for these files.

The service should integrate seamlessly with the existing designs and workflow:

To create an application:
- A client uploads the affidavit as a PDF document
- Client then enters contact details
- Client uploads the Proof of Authorization as a PDF Document
- Client then submits the application for staff review

To review an application
- Staff can view the list of pending applications from the Staff Dashboard
- Staff can open the application and view all details, including the documents
- Staff can download the documents to review (No preview within browser)
- Staff can decide whether or not the application can be approved
- If approved, the application goes back to the client for completion

To complete an application
- The client will review the details including all submitted PDF documents
- The client will make a payment
- The client's company is now registered in BC, and all submitted documents are now available in the ledger

No files, tests, or entry points are identified. Start by tracing the Queue service and the existing MinIO-backed document workflow, then locate the Document Record Service integration points used by application submission, the Staff Dashboard, client completion, and the ledger. Done means submitted PDF documents are available throughout those stated workflows.

Written by the indexing model from the issue text.