[fix] [client] Fix memory leak when publishing encountered a corner case error - #23738

…ase error (#23738)

Co-authored-by: Yunze Xu <[email protected]>
(cherry picked from commit ab1b5c0)

…ase error (#23738)

Co-authored-by: Yunze Xu <[email protected]>
(cherry picked from commit ab1b5c0)

…ase error (#23738)

Co-authored-by: Yunze Xu <[email protected]>
(cherry picked from commit ab1b5c0)

…ase error (apache#23738)

Co-authored-by: Yunze Xu <[email protected]>
(cherry picked from commit ab1b5c0)
(cherry picked from commit 7915b66)

…ase error (apache#23738)

Co-authored-by: Yunze Xu <[email protected]>
(cherry picked from commit ab1b5c0)
(cherry picked from commit 7915b66)

…ase error (apache#23738)

Co-authored-by: Yunze Xu <[email protected]>

…ls it

Two review findings on apache#26455, both queue/buffer paths left stranded by
a failure:

- processOpSendMsg's catch (from apache#23738) released only the permit and
  the memory when the body threw - realistically when the connection's
  event loop rejected the write task while shutting down. The op stayed
  in pendingMessages unrecycled, its cmd leaked both references (the
  op's own and the one retained for a write that never got queued), and
  a chunked op's ChunkedMessageCtx claim leaked with it. The catch now
  takes the op back out of the queue (OpSendMsgQueue gained a
  remove(OpSendMsg) that keeps the message-count accounting; the
  iterator's remove already did), drops the orphaned write reference,
  and releases the op's own command via releaseOpCmdAndRecycle, whose
  inline fallback covers the rejecting event loop.

- In the resend recovery loop, a rebuilt command that exceeds the max
  message size took the isMessageSizeExceeded path, which already
  released the accounting and completed the callback - but the bare
  continue left the op in pendingMessages with its fresh cmd, so it sat
  until the send timeout failed it and released the accounting a second
  time. The continue now removes the op from the iteration and releases
  its command and the op itself.

Regression test drives the real processOpSendMsg with an event loop
that rejects every task and asserts the queue is empty, the accounting
follows, and the cmd reaches refCnt 0 (fails with "expected [0] but
found [1]" queue residue on the previous code).

Assisted-by: Claude Code