fix(log-viewer): mark every row an inspector pick names, not just the rendered ones

[lukecotter]

📝 PR Overview

The mark that shows where an inspector row's frames sit was a one-shot DOM sweep over the rows a table had rendered. Tabulator builds a row's element on its first render, so the sweep could not reach a row that had never been on screen. Pick a row, then scroll down to a marked row below the viewport or expand a tree row whose children are built afterwards, and those rows arrive unmarked.

The mark now belongs to the table rather than to a list of elements: the marker records the ids it wants, and the row formatter lights a row as it stamps it. That also removes the reason a pick's mark had to wait for the view to finish moving, so the handler #974 added loses its ordering, its awaits and three of its tests.

🛠️ Changes made

• The mark is declarative — LocatedRowMarker records the wanted ids per table host, and rowIndexStamper / stampRowPath light a row as they stamp it. Every rowFormatter in the app already routes through one of those two, so no table factory needed a marker plumbed into it.
• The sweep un-lights as well as lights — it toggles rather than adds. Tabulator re-uses a row's element rather than rebuilding it, so a row can come back carrying a mark that has since moved, and a view that switches tables no longer leaves the one it left marked.
• Mark before moving — inspectorLocateHandler marks, then asks the view to move, and waits for nothing. A row the move renders lights itself. Gone with the ordering: the async body, the emphasis read-back, and the three tests that only covered which report won a race.
• A failed move is still answered, so a view that cannot reach a frame leaves no unhandled rejection.

🧩 Type of change (check all applicable)

• 🐛 Bug fix - something not working as expected
• ✨ New feature – adds new functionality
• ♻️ Refactor - internal changes with no user impact
• ⚡ Performance Improvement
• 📝 Documentation - README or documentation site changes
• 🔧 Chore - dev tooling, CI, config
• 💥 Breaking change

📷 Screenshots / gifs / video [optional]

N/A. What changes is whether a row that was never on screen is marked when you reach it.

🔗 Related Issues

Follows #974, which added the shared handler this simplifies.

✅ Tests added?

• 👍 yes
• 🙅 no, not needed
• 🙋 no, I need help

Four new LocatedRowMarker cases: a row arriving after the mark lights itself, a re-used element loses a stale mark, a table nothing has marked is left alone, and a table the mark has left stops lighting rows.

📚 Docs updated?

• 🔖 README.md
• 🔖 CHANGELOG.md
• 📖 help site
• 🧪 Marked any pre-release-only features
• 🙅 not needed

No entry: the Inspector is unreleased, so this belongs to its existing entry. Ticked to record that it was considered.

Anything else we need to know? [optional]

Where to start. log-viewer/src/components/locatedRow.ts — wantedByHost, stamp and sweep are the whole mechanism. inspectorLocate.ts is what falls out of it, now 16 lines with no async.

What does not happen, since it reads as though it should. A class on a row element survives ordinary scrolling: Row.create() is guarded by this.created, Row.initialize() deletes cells but re-uses the element, RowManager.styleRow adds and removes parity classes rather than assigning className, and our renderer only detaches and re-attaches the element. The gap is the first render, not a later one.

Why a walk up the DOM. stamp finds its table by walking parents until it meets a marked host. The alternative was threading the view's marker through four table factories to reach the formatters. The walk is a handful of nodes per row per render, against cell rendering that is orders of magnitude more, and it keeps the change inside one file.

Test plan.

• `pnpm lint` and `pnpm test`.
• Call Tree tab, inspector Call Tree → Bottom Up. Pick a caller row, then scroll the grid down past what was on screen: rows the pick names are marked when you reach them. That is the fix.
• Expand a tree row under a marked row: the children it builds arrive marked where they should be.
• Pick a row and press `Escape` quickly: the mark stays gone, including on rows you scroll to afterwards.
• Pick a row, then hover a different one: the hovered row's frames end up lit.
• Timeline dims without panning; the Database grids mark without scrolling; Call Tree and Analysis move and mark.
• Both themes, Inspector docked at the side and at the bottom.

Known unrelated failure locally. `lana/src/services/tests/servicesRuntime.test.ts` cannot resolve `effect` in a worktree not installed since #951. No `lana` file is touched here, and it passes in CI.

Follow-ups, not in this PR.

• The source filter is in nine places. Every `DetailSource`-carrying event is filtered the same way in each view; an `eventBus.onSource` would fold all nine, and with it the four near-identical `inspector:reveal` handlers, so one gesture stops needing two subscriptions per view.
• A stale move is not abandoned. Clicking two inspector rows quickly lets the earlier move settle last and scroll away from the newer row. The mark is right either way; the scroll is not, and a Tabulator expand and scroll is not cancellable.
• Whether the Database grids and the flame chart should move on a merged pick. Both can. The shared handler makes that an explicit argument rather than an accident, but changing it is a product decision.