feat: Add VSCode MCP scope support

- Add 'vscode' as a new server source type alongside 'global' and 'project'
- Implement VS Code settings discovery logic in McpHub
- Read from both 'mcpServers' and 'github.copilot.agent.mcpServers' configurations
- Add precedence logic (Project > VSCode > Global)
- Update UI components to display VSCode-sourced servers with badges
- Mark VSCode servers as read-only (cannot be edited/deleted)
- Allow enable/disable functionality for VSCode servers
- Update TypeScript types to support the new source
- Add comprehensive tests for VSCode MCP scope functionality

Fixes #8097

Author: roomote

src/i18n/locales/en/mcp.json

@@ -11,7 +11,8 @@
 		"disconnect_servers_partial": "Failed to disconnect {{count}} MCP server(s). Check the output for details.",
 		"toolNotFound": "Tool '{{toolName}}' does not exist on server '{{serverName}}'. Available tools: {{availableTools}}",
 		"serverNotFound": "MCP server '{{serverName}}' is not configured. Available servers: {{availableServers}}",
-		"toolDisabled": "Tool '{{toolName}}' on server '{{serverName}}' is disabled. Available enabled tools: {{availableTools}}"
+		"toolDisabled": "Tool '{{toolName}}' on server '{{serverName}}' is disabled. Available enabled tools: {{availableTools}}",
+		"vscode_servers_readonly": "VSCode MCP servers are managed by VS Code and cannot be modified from Roo. Please edit them in VS Code settings."
 	},
 	"info": {
 		"server_restarting": "Restarting {{serverName}} MCP server...",