Takes the publish-order locks a batch needs, in sorted key order, inside the caller's transaction. Two callers
publishing the same keys in opposite orders therefore wait for each other instead of deadlocking. Re-acquiring a
lock the transaction already holds is a no-op on both platforms, so writeMessage may ask again.
Database prerequisites (READ_COMMITTED_SNAPSHOT on SQL Server), reported once per transport by ValidateTopology.
Releases the operator's independent executor. Consumers are closed by the runtime that opened them.
Optionalopts: DatabasePublishOptions
The Database transport (03 §2.1, §7, §11). Each message is written in its own transaction on a fresh independent executor with transient retry, or inside the caller's transaction when the publish options carry an executor — in which case the caller commits and every database error propagates to it.