Skip API key resolution when Bearer token is active

When a JWT Bearer token is set, the server ignores API keys entirely.
Short-circuit ResolveActiveConnectionApiKeyAsync to avoid resolving
a stale/wrong API key during workspace switches.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: sharpninja

src/McpServerManager.Core/ViewModels/MainWindowViewModel.cs

@@ -387,6 +387,14 @@ private void ApplyActiveMcpBaseUrl(string mcpBaseUrl, string? mcpApiKey = null,
 
     private async Task<string?> ResolveActiveConnectionApiKeyAsync(WorkspaceConnectionOption option, string baseUrl)
     {
+        // JWT and API keys are mutually exclusive. When a Bearer token is available,
+        // the server ignores API keys entirely — skip the resolution overhead.
+        if (!string.IsNullOrWhiteSpace(_activeBearerToken))
+        {
+            _logger.LogDebug("[Workspace Switch] Bearer token active — skipping API key resolution");
+            return null;
+        }
+
         var normalizedTargetBaseUrl = NormalizeMcpBaseUrl(baseUrl);
 
         // Android OIDC flow injects an explicit MCP API key for the connection that completed sign-in.