fix(solid-query): attach 'useQueries' through the provider's hydration channel - #11186

🎯 Changes

useQueries never got the hydration coordination that #11168 added to useBaseQuery. It builds its own QueriesObserver and subscribes from an effect, so a component that hydrates before its dehydrated entries have arrived on the SSR stream attaches to a cold cache and refetches on mount, even for data that is well inside staleTime.

The subscription now goes through the same coordinator. With a provider in place, useQueries attaches once every one of its queries has been primed, or once the channel reports itself done. One QueriesObserver covers all of the queries, so it can only attach when the last one is ready. QueryClientProvider closes the channel right away on a fresh client mount, detected with the same Promise executor probe useBaseQuery uses, so an app without SSR never waits.

For the test, the streaming fixture gains a useQueries in the shell whose query settles after the slow boundary, so its entry only rides the final flush. Before the change it refetches at shell hydration.

Fixes #11185

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally.

Local verification: vitest run on solid-query (330 tests), solid-query-persist-client and solid-query-devtools, all green with no type errors; eslint and prettier clean.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.