Migrate Name Request "Consumed" Status Update to GCP Pub/Sub Queue

Currently, the "consumed" status for Name Requests is updated via a direct REST API call from multiple applications/filings. This has led to inconsistencies where some updates are missed or fail silently due to concurrency or reliability issues.

To improve reliability, traceability, and decoupling, we will transition to using Google Cloud Pub/Sub as a message queue. All applications will publish a message when a Name Request should be marked as "consumed." A dedicated worker service will subscribe to the topic and process updates reliably.

for more background info, refer to https://app.zenhub.com/workspaces/names-team-board-new-655554cbddd49510027dad2e/issues/gh/bcgov/entity/26250

Start by locating the applications and filings that currently update Name Request "consumed" through direct REST calls, then review the related background issue for context. Done means those publishers and a dedicated Google Cloud Pub/Sub worker support reliable, traceable consumed-status updates, but this issue names no files or tests to run.

Written by the indexing model from the issue text.