Amazon Q Chat Re-Adds Disabled MCP Servers After VSCode Updates, Leads to Context Window Overflow

## Problem

## Steps to reproduce the issue

1. Disable some MCP server(s).
2. Update VSCode.
3. Continue Amazon Q chat on a previous conversation.
4. Realise your context window gets immediately overflowed.
5. [OPTIONAL] Scratch your head as to why for 10 seconds to 10 minutes, depending on how many times you've suffered through this already.
6. Check your MCP Servers list to see your disabled MCP server(s) are enabled again.
7. Realise you'd disabled your MCP server(s) since they're too large and were hogging your context window.
8. [OPTIONAL] Colourful language.

## Expected behavior

1. Disable some MCP server(s).
2. Do anything imaginable. Any combination of things. Go wild.
3. MCP server(s) stay disabled.
4. You're slightly less annoyed by the UI.

## System details (run `AWS: About` and/or `Amazon Q: About`)

OS: Darwin x64 24.4.0
Visual Studio Code extension host: 1.104.2
Amazon Q: 1.96.0
node: 22.18.0
electron: 37.3.1

Start by reproducing the issue in the Amazon Q VSCode extension: disable MCP servers, update VSCode, and resume a previous chat. Inspect how the MCP Servers list restores its state; done means disabled servers remain disabled after updates and do not immediately overflow the chat context window.

Written by the indexing model from the issue text.