Extension host repeatedly crashes (exit code 134 / SIGABRT) when built-in GitHub Copilot Chat activates

## Issue
The extension host crashes repeatedly (SIGABRT, exit code 134) a few seconds after startup, right when the built-in GitHub Copilot Chat extension finishes activating. This makes VS Code unusable (all extensions crash together with the host, and sign-in flows are interrupted).

- Copilot Chat Extension Version: 0.63.0 (built-in)
- VS Code Version: 1.135.0 (stable, commit 08d4889f9e)
- OS Version: Windows 10 Pro 22H2 (build 22621.4317)
- Feature (e.g. agent/edit/ask mode): N/A - crash occurs during Copilot Chat activation, not tied to a specific feature
- Selected model (e.g. GPT 4.1, Claude 3.7 Sonnet): N/A
- Logs:
- `Extension host with pid X exited with code: 134, signal: unknown.`
- `[UtilityProcess id: 1, type: extensionHost, pid: X]: crashed with code 134 and reason 'crashed'`
- Copilot Chat output right before crash (earlier sessions): `Failed to create database. Falling back to in-memory db: Error: unable to open database file`
- Copilot Chat output (later sessions): repeated `GitHub login failed`
- Last Copilot Chat log line before crash: `Setting context key: github.copilot-chat.activated`

Steps to Reproduce:
1. Use VS Code 1.135.0 (stable) with the built-in GitHub Copilot Chat enabled and signed in.
2. Open a trusted workspace (e.g. one where Copilot Chat was previously used).
3. The extension host crashes about 2-3 seconds after startup, right after Copilot Chat activation completes; it auto-restarts and crashes again in a loop.

Notes:
- Disabling the `github.copilot-chat` extension completely stops the crashes; all other extensions work normally.
- Reproduced after a clean reinstall of VS Code 1.135.0.
- Does not occur in a fresh profile where Copilot Chat does not activate (no sign-in).