feat(MK8S-196): expose shared QueryClient to MCP tools via ToolContext

[JBWatenbergScality]

Summary

• Add queryClient: QueryClient to ToolContext so federated apps' MCP tools can keep chat-side panels in sync after mutations.
• Populate it in MCPRegistrar from the shell-ui-owned queryClient exported by FederatedApp.tsx.

Follow-up to merged PR #4820 (branch was kept alive). Pairs with:

• scality/data-browser#367 — per-tool cache-sync via injected QueryClient
• feat(mcp): wire host basePath, two-stage SigV4, account cache, arg coercion zenko-ui#1185 — targeted invalidation in zenko's MCP tools

Why

The previous wrapper-side approach (zenko-ui's withQueryCacheInvalidation) called invalidateQueries() with no arguments after every non-readonly tool, blowing the entire cache — including auth queries — and leaving the UI empty. Injecting the QueryClient lets each tool target only the keys it actually affects.

Test plan

• Type-check passes (`npm run check-types`).
• Manual E2E on the ARTESCA test cluster: agent-driven `createBucket` refreshes the bucket panel without empty-UI regression.

🤖 Generated with Claude Code

[bert-e]

Hello jbwatenbergscality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.