Feature: Support VS Code user-profile `mcp.json` for `--global` scope

[sergio-sisternes-epam]

Summary

Issue #637 named VS Code user-profile mcp.json as in-scope for --global MCP installation. However, the implementation in PR #638 marks VS Code as workspace-only (supports_user_scope = False) because the current VS Code adapter only writes to .vscode/mcp.json (project-local).

VS Code does support a user-level MCP configuration path (e.g. ~/.config/Code/User/settings.json or the VS Code user-profile mcp.json), but the adapter does not currently implement this.

Proposed Change

1. Investigate the correct user-profile MCP configuration path for VS Code (varies by platform: Linux, macOS, Windows).
2. Add a user_scope_config_path property (or similar) to VSCodeClientAdapter that returns the user-level config path.
3. Set supports_user_scope = True on VSCodeClientAdapter once the user-profile path is implemented.
4. Add tests for the new behavior.

Context

• Parent issue: [BUG] apm install --global skips MCP server installation for all runtimes #637
• Related PR: Fix apm install --global skipping MCP server installation #638 (marks VS Code as workspace-only as a pragmatic scope cut)
• The Copilot CLI and Codex CLI adapters already support user scope via ~/.copilot/ and ~/.codex/ respectively.

Labels

enhancement