Document Record Service Corps Integration Backwards Compatibility

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

In order for all filings to remain fully backwards compatible with paper forms, Registries Staff must be able to input a barcode id as part of the final review/confirm/pay step.

The Document ID component should be present with the ability to either provide a barcode id as text input, or select a checkbox to indicate that the DRS should generate an ID automatically.

In any case where the Document ID is not present, the API should behave as if a generate id checkbox was selected. In other words - only use a barcode id if one was explicitly provided.

https://www.figma.com/design/w5TkwamvwzxxO35pXJG7bK/DRS-%7C-CORPS-Integration?node-id=2967-2

Start with the final review/confirm/pay flow and the linked Figma design for the Document ID component, then trace the corresponding API request. Done means staff can enter a barcode or choose automatic generation, while an omitted Document ID behaves as an explicit generate-ID choice and an explicitly supplied barcode is preserved.

Written by the indexing model from the issue text.