fix: preserve user input when tool execution fails

[roomote]

Description

This PR attempts to address Issue #9341 where user messages disappear when an editing error occurs during the Save/Reject prompt.

Problem

When users type a message during a file edit approval prompt and an editing error occurs, their message disappears instead of being preserved. This forces users to retype their message, which is frustrating especially for longer messages with important context.

Solution

Modified the ChatView component to:

• Not clear the input immediately when the user clicks Save/Approve
• Only clear the input after successful tool execution (when api_req_started is received)
• Preserve the input when errors occur, allowing users to retry without retyping
• Still clear input when user explicitly rejects (since that's an intentional action)

Changes

• Modified to not clear input state immediately
• Added logic to clear input only after successful api_req_started
• Added comprehensive tests to verify the input preservation behavior

Testing

• Added new test suite with 4 test cases
• Verified existing ChatView tests still pass
• Tests cover:
  • Input preservation on tool errors
  • Input clearing on explicit rejection
  • Input clearing on successful execution
  • Multiple sequential errors

Fixes #9341

Feedback and guidance are welcome!

[roomote]

Rooviewer   See task on Roo Cloud

I've reviewed this PR and found an issue with the scope of the input preservation changes.

Issues Found

• Input clearing was removed for ALL ask types in handlePrimaryButtonClick, but the clearing logic only handles tool asks. This means commands, browser actions, and MCP server operations will never clear their input, even on success.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

The input preservation logic is applied too broadly. Input is no longer cleared for ANY approval in this switch (including command, browser_action_launch, use_mcp_server, etc.), but the clearing logic on lines 384-393 only handles tool asks. This creates inconsistent behavior where approving a command or browser action will preserve the input even on success, causing it to never be cleared.

The fix should only skip clearing input for tool asks, since the issue #9341 specifically mentions file editing errors. Other ask types should clear input immediately on approval as they did before.

_{Fix it with Roo Code or mention @roomote and request a fix.}