feat(inspector): split the row limits by SObject on the Database tab

[lukecotter]

The Database tab said how long the queries took but never how close the log came to the row limits, or which SObject filled them. A user near 50,000 query rows had to read the grid row by row to find out.

This adds a Row budget section: one bar per row limit, split by the SObject that holds the rows, with the space left as the headroom and a mark where the limit falls. The Database whole-log view would then read five sections, more than the tab can carry, so the section ships written and tested but not registered. Re-adding it is one comment in detailSections.ts.

Changes

• rowBudget.ts — the rows against each limit by SObject, the statement counts, and the worst single search; the governor peak answers where the log holds one, else the observed rows do
• database-rows — the bars, the counts line, and a note when a certified package's own limits let a figure pass 100%
• StackedTimeBar — takes a formatter, so a row-count bar reuses the time bar, and marks where a limit fell
• databaseSections.ts — the call tree is last in every inspector view, so the panel reads the same wherever the selection came from
• global.styles.ts — a shadow root no longer keeps the browser's paragraph margin
• Docs and CHANGELOG follow the render order

Test plan

• pnpm lint and pnpm test (1804 tests, 133 suites)
• pnpm build, then the Database tab in the dev host, light and dark, side dock and bottom dock: the tab shows Namespace duration, Database duration and Call tree, and no Row budget