[BUG] Sync API setConfiguration through provider state wiring

[easonLiangWorldedtech]

Problem

API.setConfiguration() does not properly propagate configuration changes to the provider local state. When a user updates their API configuration (model, temperature, etc.), the change is not reflected in the running webview instance because:

1. API.setConfiguration() was not calling the provider's setValues() method
2. Provider state and API state were out of sync after configuration changes
3. No test coverage existed for this critical wiring path

Solution

Wire API.setConfiguration() to call the provider's setValues() method, ensuring configuration changes propagate correctly:

• API.setConfiguration() now calls provider setValues() to update local state
• Added comprehensive API state wiring test covering the full propagation chain
• No dead code: setupGlobalStateListener was intentionally not included because mode/profile changes use ContextProxy / global state, not VS Code onDidChangeConfiguration events

Scope

• API.setConfiguration() → provider setValues() wiring
• API test coverage for configuration propagation
• Clarification on why setupGlobalStateListener is not shipped (mode/profile use ContextProxy/global state, not VS Code configuration events)

Tests

• Targeted API/webview/provider tests: 152 passed

Related

• Old Issue [BUG] Multi-tab mode/model settings get overwritten by latest task #908 (historical context)
• Old PR fix(webview): isolate parallel provider view state #909 (parent PR)