fix(SorokitProvider): handle disconnect errors, re-init client on network switch

[KayProject]

Resolves #405

1. disconnectWallet no longer leaks an unhandled rejection

await client.wallet.disconnect() had no catch, so an adapter that throws (extension disconnected mid-session) escaped through the useCallback as an unhandled promise rejection.

It's now caught and reported via the existing reportError path, and the session is still torn down — the user asked to disconnect, so address, account, and balances are cleared regardless.

One ordering detail worth flagging: the report is deliberately emitted after setErrorHistory([]). Reporting first meant the fresh-session history reset immediately wiped the very error we'd just recorded.

2. getClient() now reflects the current network

After a successful switchNetwork, setNetwork(data) updated React state but the getClient() singleton still handed back a client pointed at the previous network — so getClient().transaction.submit() after a switch went to the old endpoint.

Two parts:

• A successful switch re-initialises the singleton. The new optional createClientForNetwork?: (network: NetworkInfo) => SorokitClient prop builds the replacement client; without it, the current client is simply re-registered.
• The provider now calls initClient(client) when its client prop settles or changes.

That second point is worth calling out: initClient was not called anywhere in src/ before this change, so getClient() would throw "Client not initialized" for any component that reached for it outside of tests. The provider registering its own client closes that gap.

3. New onNetworkChange prop

Fires after every successful switch with the new NetworkInfo, so consumers can clear caches or re-subscribe to feeds without watching network in an effect and depending on internal state shape. It does not fire when the switch fails.

Both new callbacks are held in refs, matching the existing onError pattern from #353, so a parent passing fresh inline functions each render doesn't destabilise switchNetwork's identity.

Verification

npx vitest run src/context/SorokitProvider.test.tsx — 26 passed, including 7 new cases: disconnect failure surfaced + state still cleared, non-Error rejection fallback message, singleton wired on mount, singleton swapped via the factory on switch, singleton preserved without a factory, onNetworkChange fires on success, and does not fire on failure.

	Test files	Tests
main (5bc3678)	24 failed / 51 passed	61 failed / 945 passed
this branch	24 failed / 51 passed	61 failed / 952 passed

No regressions.

Heads-up on the build AC

npm run build / tsc -b do not pass on main independently of this change — FeeEstimator.tsx and SorobanPanel.tsx each have an unclosed block from a merge, which is also what the 61 pre-existing test failures are. Glad to send a separate PR repairing those.

ESLint clean on all changed files.

[drips-wave]

@KayProject Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits