feat: DBRowSidePanel global error boundary

[ernestii]

Add a global error boundary to DBRowSidePanel.

In order to show the error boundary inside the drawer, I had to split the component into
"inner" and "drawer/container" sections.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 38091e3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hyperdx-v2-oss-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 23, 2025 3:57pm

[Copilot]

Pull Request Overview

This PR introduces a global error boundary around the DBRowSidePanel drawer by splitting the component into an “inner” renderer and a “container” that handles the Drawer and error fallback.

• Added DBRowSidePanelErrorBoundary to encapsulate Drawer logic, state management, and render an error UI.
• Refactored the original DBRowSidePanel into an inner component that receives a new setSubDrawerOpen prop.
• Updated conditional rendering for loading, success, and error states, and removed legacy query‐param and resize logic from the inner panel.

Comments suppressed due to low confidence (2)

packages/app/src/components/DBRowSidePanel.tsx:1

• Several hooks and utilities used later (useState, useQueryState, parseAsStringEnum, useZIndex, useResizable) are not imported here. Please add those imports to avoid build errors.

import { createContext, Dispatch, SetStateAction, useCallback, useContext, useMemo,

packages/app/src/components/DBRowSidePanel.tsx:411

• [nitpick] Using _ as a bound variable can be unclear. If you intend to ignore the first value, you can omit it via [, setQueryTab] or give it a more descriptive name.

const [_, setQueryTab] = useQueryState(