fix(sdk): detach the per-turn message listener when dropping a stale channel interaction

A duplicate or late channel interaction (e.g. a repeated Slack approval
click) whose toolCallId matches no pending tool call was dropped without
detaching the per-turn session.in listener. That listener marks inbound
records CONSUMED, so after the drop the next user message was swallowed
into pendingWireMessages (already drained before the wait) and the turn
idled until the timeout, ending the run and losing the message.

Mirror the action path: detach msgSub and decrement turn (a dropped
interaction is not a turn) before falling through to the wait.

Author: ericallam

packages/trigger-sdk/src/v3/ai.ts

@@ -7594,6 +7594,11 @@ function chatAgent<
                   turn--;
                 }
 
+                if (droppedStaleInteraction) {
+                  msgSub.off();
+                  turn--;
+                }
+
                 if (!isAction && !droppedStaleInteraction) {
                   // Mint a scoped public access token once per turn, reused for
                   // onChatStart, onTurnStart, onTurnComplete, and the turn-complete chunk.