fix(web): re-enable Add connector button without waiting on background refetch

The "Add connector" button stayed disabled for 2-3s after creating a
connector because the create handler awaited invalidateMcpConfigurationQueries,
which blocks on refetching the server-status and tools queries (network
round-trips to the MCP servers). Fire those invalidations in the background
(void) so the button re-enables as soon as creation succeeds, matching the
fire-and-forget invalidation pattern used elsewhere in the codebase.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: msukkari

packages/web/src/app/(app)/settings/workspaceAskAgent/workspaceAskAgentPage.tsx

@@ -293,7 +293,10 @@ export function WorkspaceAskAgentPage({ callbackStatus, callbackServer, callback
                 return;
             }
 
-            await invalidateMcpConfigurationQueries(queryClient);
+            // Fire-and-forget: the server list / connection status / tools queries
+            // refetch in the background (some hit the MCP servers over the network and
+            // take a couple seconds). Don't block re-enabling the button on them.
+            void invalidateMcpConfigurationQueries(queryClient);
             handleCloseClientCredentialsDialog();
         } catch {
             toast({ title: "Error", description: "Failed to add connector.", variant: "destructive" });
@@ -339,7 +342,9 @@ export function WorkspaceAskAgentPage({ callbackStatus, callbackServer, callback
                 return;
             }
 
-            await invalidateMcpConfigurationQueries(queryClient);
+            // Fire-and-forget: see note in the static-OAuth path above. Re-enabling the
+            // button shouldn't wait on the background status/tools refetch.
+            void invalidateMcpConfigurationQueries(queryClient);
             onSuccess?.();
         } catch (error) {
             toast({ title: "Error", description: `Failed to add connector: ${error}`, variant: "destructive" });