Improve Pub/Sub publishing latency for the migrated customer portal that shows timeouts but no publish errors.

Disabling Pub/Sub message batching improves publishing latency by sending each message individually without waiting for a batch to fill or a batching timeout to expire. This reduces the time between a message being ready for publication and its actual transmission, directly addressing timeouts caused by delays in the publishing process. Increasing the Pub/Sub total timeout retry value would only allow more time for an operation to complete, potentially masking the underlying latency issue rather than resolving it. Switching from a subscriber pull model to push affects message delivery to subscribers, not publishing latency from the publisher. Creating a backup Pub/Sub queue is a strategy for disaster recovery or redundancy, not for improving publishing performance.