Add UI entry point for terminal auto-approve dropdown

[Copilot]

This PR adds a dropdown menu to the terminal command confirmation dialog, allowing users to quickly configure auto-approval settings for commands. Previously, users had to manually edit settings to add commands to the auto-approve list - now they can do it directly from the confirmation dialog.

Implementation

When a terminal command requires confirmation, the "Continue" button now includes a dropdown with contextual options:

• Always allow [exact command] - Adds the specific command to the auto-approve list
• Always allow [base command] commands - Adds the base command (e.g., npm) to approve all commands starting with it (only shown for multi-word commands)
• Configure auto approve... - Opens the settings page for advanced configuration

Similar to workspace trust dialogs, the dropdown provides smart options based on the command structure:

// For "npm run build":
[
  { label: "Always allow `npm run build`", type: "exact" },
  { label: "Always allow `npm` commands", type: "prefix" }, 
  { label: "Configure auto approve...", type: "configure" }
]

// For single commands like "git":
[
  { label: "Always allow `git`", type: "exact" },
  { label: "Configure auto approve...", type: "configure" }
]

Technical Details

• Extended IToolConfirmationMessages interface with customActions property
• Added _generateAutoApproveActions() method in RunInTerminalTool to create contextual dropdown options
• Enhanced ToolConfirmationSubPart to handle custom actions and update the chat.tools.terminal.autoApprove configuration
• Leverages existing moreActions dropdown infrastructure from the confirmation widget
• Includes comprehensive tests for various command scenarios

The feature integrates seamlessly with the existing auto-approval system and maintains consistency with VS Code's confirmation dialog patterns.

Fixes #253268.

Warning

Firewall rules blocked me from connecting to one or more addresses

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

• electronjs.org
  • Triggering command: node-gyp (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)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.