User is presented with just a spinner for a longtime when clicking on "Save" option presented after entering configuration (after upgrade) and the `update required` continues to be present after save is done (until manual refresh)

[sangee2004]

Describe the bug
User is presented with just a spinner for a longtime when clicking on "Save" option presented after entering configuration (after upgrade) and the update required continues to be present after save is done (until manual refresh)

To Reproduce

1. As admin, Create composite MCP server with few MCP servers.
2. As regular user, connect to this composite MCP server
3. Chat with this composite MCP server.
4. As admin , Update composite MCP server and add another MCP server to this composite MCP server that has required configuration parameters.
5. Upgrade the composite MCP server instance created from step 2.
6. As regular user, go to the project that was created from step 3.

User will be presented with configuration page to enter credentials for the newly added MCP server.
Enter credentials and click on Save

Notice that user will be in the state for a very long time when /configure api call is in progress (like 30 sec to 1 minute)

Even after "Save" is done , user will be presented with upgrade required for the composite mcp server (until manual refresh)

https://www.loom.com/share/56e987d2b4974fab99a80e2c9fa3b763

Expected behavior

During the time update is happening user should be presented with some progress bar similar to what gets presented when user connected to composite MCP server for the first time.

Once update is done , upgrade required notification for the composite mcp server should be cleared.

[njhale]

I will look into this, but I don't think it's a blocker for 0.13 (since the status is cleared on refresh and everything does work), but @cjellick could correct me there.

[sangee2004]

Logged a separate issue to track configure api taking very long in this case - #4935