Table Editor Sidebar Crash Due To Missing QueryClientProvider

The row expansion sidebar (or a child component) relies on React Query hooks to fetch data, but it is rendered via a portal or a separate React root that is not wrapped by the application's QueryClientProvider. This results in the hook being unable to access a QueryClient instance.

1. Open Supabase Studio and navigate to the Table Editor. 2. Select a table that exhibits the issue (specific tables with certain column types or filters). 3. Optionally apply a filter. 4. Click on a row to expand it and open the update sidebar. 5. Observe the client-side exception in the browser console.

If the sidebar is wrapped with a new QueryClient instance instead of reusing the existing one, cache data and mutations may become inconsistent, leading to stale data or duplicate requests. Ensure the same QueryClient instance is used across the app. Additionally, if the provider is added multiple times, nested providers are fine as long as they share the same client. Rollback: if this fix introduces issues, revert to the previous rendering approach and investigate why the sidebar lost the context (e.g., portal outside root or a separate React root).