DRS - Business Filings UI - Document Id Component

- Creating Placeholder Ticket, not positive if we agreed on this being required yet ...

***Staff Only***
- Include for CORPS
- Implement a Document ID component or some equivalent to capture potential Barcoded Paper document identifiers
- Option to Generate Doc ID instead
- Include additional Document Id in filing payloads or as query param. ( This may also require further updates in Legal Api to pass along to the DRS Hook)
- Submission **(How do we submit? Query param, payload? Or additional property on DRS side)**
- Validation (for CORPS)

- For scope context: This is an older UI / Vue versions etc - will require a new component to be built for the most part, although a lot of functionality can be ported over.

Repo: https://github.com/bcgov/business-filings-ui

Filings Map:
- AGM Extension
- AGM Location Change
- Amalgamation Out
- Amalgamation Selection
- [x] Annual Reports
- Consent Amalgamation Out
- Digital Credentials
- Notice of Withdrawl
- [x] Director Filings
- [x] Address Filings
(Entity Types: Only include for Corps)

Confirm with maintainers whether the Document ID is required and whether it belongs in the filing payload or query parameters. Then review the business-filings-ui components for Annual Reports, Director Filings, and Address Filings, along with the Legal API and DRS Hook references; done means the agreed CORPS filings support capture or generation, validation, and submission of the identifier.

Written by the indexing model from the issue text.