Fix CLI becoming unresponsive during interactive selection dialogs

[Copilot]

Problem

The CLI would become completely unresponsive when users encountered interactive selection dialogs, such as shell command confirmation prompts. Users reported that when presented with numbered options (1, 2, 3), the CLI would appear "frozen" and not respond to any keyboard input, requiring them to forcefully terminate the process.

Root Cause

The issue was caused by multiple useKeypress hooks being active simultaneously, creating conflicts in terminal raw mode control:

1. ShellConfirmationDialog used its own useKeypress hook for escape key handling
2. RadioButtonSelect component used another useKeypress hook for selection navigation
3. ToolConfirmationMessage had the same pattern with escape and Ctrl+C handling

When both hooks were active, they interfered with each other's stdin raw mode setup, preventing keyboard events from being properly processed.

Solution

This PR consolidates keyboard input handling to eliminate the conflicts:

• Enhanced RadioButtonSelect: Added onEscape and onCancel callback props to handle keyboard shortcuts internally
• Simplified ShellConfirmationDialog: Removed redundant useKeypress hook and delegated escape handling to RadioButtonSelect
• Fixed ToolConfirmationMessage: Removed duplicate useKeypress hook and added both escape and Ctrl+C handling via RadioButtonSelect callbacks

The fix ensures only one useKeypress hook controls stdin at a time, preventing the conflicts that caused the frozen behavior.

Testing

• All existing tests continue to pass
• Components using RadioButtonSelect (ShellConfirmationDialog, ToolConfirmationMessage) maintain full functionality
• Users can now properly navigate selection dialogs using:
  • Arrow keys or j/k for navigation
  • Enter or number keys for selection
  • Escape to cancel
  • Ctrl+C for cancellation

Fixes #452.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• gb4w8c3ygj-default-sea.rum.aliyuncs.com
  • Triggering command: node (vitest 2) (dns block)
  • Triggering command: node (vitest 3) (dns block)
  • Triggering command: node (vitest 1) (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

@pomelo-nwu 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.