fix(cli,vscode): invalidate caches on config update and sync marketplace/settings state

[markijbema]

Summary

• Fixes stale per-instance config after Config.updateGlobal() — active instances now pick up global config changes (modes, providers, models, etc.) without requiring a server restart
• Adds State.resetCaches() which clears all cache-only Instance.state entries across all instances without tearing down side-effectful resources
• Fixes marketplace installed state not updating when removing a mode from the settings panel
• Fixes newly installed marketplace modes not appearing in Agent Behaviour settings

Problem

PR #7172 correctly removed Instance.disposeAll() from Config.updateGlobal() to stop it from destroying sessions, MCP connections, and in-flight operations on every config change. However, this left a gap: global.reset() only invalidates the process-wide global config lazy cache, not the per-instance Config.state (or downstream caches like Agent.state, Provider.state, etc.) that merge global config at initialization time.

This meant that after a global config change via the VS Code settings panel (e.g. changing default agent, provider, or model), the server's HTTP endpoints (/config, /app/agents, /app/providers) would continue returning stale cached data. The extension would re-fetch after the global.disposed SSE event, but get back the old values.

Additionally, marketplace install/remove operations only refreshed the agents list but not the config context or marketplace metadata, causing:

• Settings panel showing stale agent data after marketplace changes
• Marketplace showing modes as still installed after removal from settings

As noted by the review bot on #7172: comment

Fix

CLI (State.resetCaches): Iterates all instance state maps and deletes entries that have no dispose callback. These are the 18 "pure cache" entries (Config, Agent, Provider, Tool, Skill, Command, Format, Plugin, etc.) that are safe to drop and will be re-computed on next access. The 9 entries with dispose callbacks (Prompt sessions, MCP connections, LSP clients, PTY processes, file watchers, etc.) are preserved.

The flow after the fix:

updateGlobal() writes config to disk
  → global.reset()           // clear global config lazy cache
  → State.resetCaches()      // clear all per-instance derived caches
  → emit "global.disposed"   // SSE to extension
  → extension re-fetches     // HTTP requests hit server
  → Config.state() re-inits  // fresh merge with updated global config
  → Agent.state() re-inits   // fresh agent list
  → UI updates correctly

Extension (refreshAfterMarketplaceChange): After every marketplace install or remove, pushes fresh agents, config, and marketplace metadata to the webview in parallel. Previously only agentsLoaded was sent, leaving the config context stale — so config().agent in the settings view wouldn't reflect the change until the fire-and-forget SSE reloadAfterAuthChange happened to complete.

Extension (handleRemoveMode): Calls refreshAfterMarketplaceChange after removing a mode from the settings panel, so the marketplace view immediately reflects the removal.

[marius-kilocode]

Looks dangerous