Filer DRS document record update — publish to drs update topic

[mruff-aeq]

From bcgov/lear#4618 review: filer calls update_document_records after the filing transaction commits — sync PATCH through the API, failure only logged, no retry. Same weakness as namex consume and business profile update_entity.

Two options raised in the review thread:

• A: publish message to a DRS queue and process there (like publish_drs_create_message, new topic e.g. doc-api-app-update-record)
• B: make post-transaction actions retryable sub-tasks of business-filer

Option A - Selected Option

Verify which path, define what work is needed, then implement. Changes may span legal-api and queue services.

[mruff-aeq]

Early notes: filer worker is pub/sub push — nack replays the whole committed filing, so B needs persisted sub-task state and idempotent re-entry across all post-commit actions. A is smaller but publish_drs_create_message is not copy-paste (hardcodes documentClass CORP, per-filing not per-document, no filing date in payload) and needs a payload contract + consumer on the DRS side.

[kialj876]

Dougs comment:
'I will set up a new topic named doc-api-app-update-record. The filer can then switch to publishing on this topic in a separate. PR'

I think that simplifies our side we just need to coordinate with him on what payload is expected for that topic

[meawong]

This ticket tracks Doug's work on the DRS side: https://app.zenhub.com/workspaces/colin-egress-team-6904d552be2bb0000fa13ad6/issues/gh/bcgov/entity/34399