DRS Improvements

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

Scaling up the Document Service MVP so that it can better serve the needs of Registries Staff. Points to consider:
- Integration with greater number of products,
- More robust RBAC (not available to citizens, available to entities owners, available to public, available for a fee, etc)
- Refined UI
- Data Migration from SOFI
- Integration with Legacy Applications

----
## Current State
- The MVP of the Document Service exists as a standalone application with a UI that allows for the creation, searching, and editing of document records. It is backed by an API that can be consumed by other registries applications.
- As a standalone application, Registries Staff would have to manually enter in all data from their registry, including barcode ids and document types, which provides no difference in how the legacy system operates.

----
## RC/GA Identification
Full General Acceptance state of the mature product would include complete automated integration via the Doc Service API with:
- Cont. In
- MHR
- Names (removed from scope in December)

No files or tests are named. Start by reviewing the standalone Document Service UI and API, then confirm scope for integrations with Cont. In and MHR, RBAC, SOFI migration, and legacy applications. Done requires explicit scoped acceptance criteria for the selected improvement; this issue is too broad to implement as written.

Written by the indexing model from the issue text.