fix: use the app's QueryClient in useConnect/useAddToNetwork

[gomesalexandre]

closes #3052

bug

useConnect and useAddToNetwork each build a new QueryClient and invalidate it:

const queryClient = new QueryClient();
// ...
onSettled: () => { queryClient.invalidateQueries(); }

That client is disconnected from the one in pages/_app.js (<QueryClientProvider client={queryClient}>), so invalidateQueries() invalidates an empty, unused cache. After connecting a wallet or adding a network, the app's queries never refetch.

fix

Use useQueryClient() to get the client from context, so the invalidation targets the app's real cache. Two-line change in each hook (react-query v4, useQueryClient is the v4 hook).

receipts

next build  →  ✓ Compiled successfully

Both hooks call useQueryClient() unconditionally at the top of the hook (rules-of-hooks safe), and the QueryClientProvider in pages/_app.js supplies the client.