Document Record Service MHR Product Integration

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

As a Registries Analyst working with the MHR, I want to be able to have a new document record created automatically and be associated with the filing and ready for document upload, scan, or both

The service should integrate seamlessly with the existing designs and workflow

1. Staff provide a barcode number if the documentation requires scanning, or selects "Generate Id" (almost all cases staff must work from a form provided by a client/citizen)
2. Staff work through all required fields for the filing
3. Upon final submission, the MHR app makes an API call to create the Doc Service with Filing/Registration ID
4. A link to the Doc Service is available from the product table and registration/filing information page

Staff follow that link or use the search capability in the document service to upload a batch of document related to the filing.

### [Figma Design](https://www.figma.com/design/QScdxvCqzEmuC1RnV9vvyU/Document-Record-Service?node-id=1964-28520)

Start by tracing the MHR app's final filing submission flow and the existing product table and registration/filing information page. Review the linked Figma design and determine how the Doc Service API, Filing/Registration ID, barcode or generated ID, and document-service link fit together. Done means the workflow creates and associates the document record and exposes the link described in the issue.

Written by the indexing model from the issue text.