Skip redundant send_to_terminal confirmation when replying to askQuestions carousel

[meganrogge]

Fixes #309589
Fixes #309608

When an interactive command (e.g. npm init) waits for input in default approvals mode, the agent calls askQuestions to collect user answers, then sends each answer via send_to_terminal. Previously, a send_to_terminal call could show a confirmation dialog, even though the user just explicitly provided that text through the askQuestions UI.

This skips the confirmation when we can correlate the send_to_terminal text to a recently answered question carousel for the same terminal.

Changes

Confirmation skip — _getQuestionContextForTerminal already returns the question text for the "(replying to: …)" display. A non-undefined result now also signals that confirmation is unnecessary. forceConfirmationReason still takes precedence, and autopilot mode behavior is unchanged.

Exact answer matching — Previously, _getQuestionContextForTerminal had shortcuts that could return a question without verifying the command matched the answer (single-question shortcut, multi-question fallback). This meant any send_to_terminal call could bypass confirmation whenever a recent carousel existed for that terminal. Now the method only returns a question when the command exactly matches the answer at the correct position.

Positional matching — When all answers are identical (e.g. pressing Enter to accept every default in npm init), answer-value matching always returned the first question. The method now counts prior send_to_terminal tool invocations after the carousel to determine the positional index, so the progress message correctly shows "Package name?" → "version?" → "description?" instead of repeating "Package name?" for every prompt.

demo-prompt-input.mov

[meganrogge]

closing as we're not doing candidates probably