[CloudCorpRecords]

Fixes #120.

Activate/deactivate and the Refresh action called refetch() after their API calls. That sets the page-level isLoading flag, which unmounts the whole ServersTable behind a spinner and reads as flicker.

This applies the same targeted-patch approach Tools.tsx uses in handleToggleTool: after the mutation the page re-reads just the affected server (serversApi.get, with the single-server request cache invalidated first) and patches it into local state and the query cache. The table never unmounts, so there is no spinner and no flicker.

Changes:

• src/pages/Servers.tsx: new patchServer callback; handleToggleEnabled and handleRefresh use it instead of refetch(). refetch() is still used for delete, OAuth authorize, and the create/edit form, which need a full list.
• src/api/servers.ts: new serversApi.invalidateGetCache(id) so the re-read after a mutation does not return the pre-mutation cached snapshot.

Tests:

• src/pages/Servers.test.tsx: rewrote the toggle test to assert the single server is re-read and patched with no list refetch and no spinner; added a refresh test asserting the row counts update with no list refetch. Both fail against the unfixed code (red-checked).
• src/api/servers.test.ts: added a test for invalidateGetCache.
• Full suite: 227 files, 3790 passed, 1 skipped (the extra api test ran green separately).
• tsc -b clean (after orval generate); eslint clean on all changed files.

[marekdano]

@CloudCorpRecords - thanks for your contribution!
The core fix directly solves the issue and follows existing patterns in the codebase.

LGTM 🚀

[vishu-bh]

Clean implementation and solid code.

LGTM 🚀