fix(ui): the card's channel name is a real link too; call sites the bug hunt left untested now have tests

Deep-review R6 — the small items:

- The video card's channel name was still a <button> (pre-existing): ctrl/middle-click did nothing
  there while the title above it and the player's channel name honoured them. It renders through
  ChannelNameLink now, which grew a forwarded ref (the clamp measurement), pass-through attributes,
  a `tooltip`, and an opt-in `stopPropagation` so no click reaches the card's row.
- ChannelNameLink rendered an empty, still-tabbable <a> for a channel with no title yet (a stub first
  seen through a live search; pre-existing at this site). It falls back to the translated "Channel".
- The feed's SortKey→SortOption mapping existed twice in Feed.tsx; one `feedSortOptions` in
  feedSort.ts serves both modes (DIRECTIONLESS is module-private again).
- The backfill refresh's comment claimed a one-page cost. It refetches every loaded page of the
  grid, and that is the right price: backfilled videos are older, so they land below the head.

Tests for call sites that could be deleted with every lane green: the channel page running the
backfill refresh (knip had been blinded by the hook test's import), Feed handing the grid the live
results in the chosen key AND direction, the card using the link. Plus the alt-click arm of the shared
click predicate, and a plex filter-chip test that claimed it made no request while firing a real one.
Verified on localdev: the feed's channel names are anchors (same 14 px muted look), a plain click
opens the channel in-app. 7 mutations, each red on its assertion.

frontend/src/lib/channelDetailPoll.ts

@@ -37,10 +37,13 @@ const backfillChangedCatalog = (
  *  background job has written a row — which is why the list stayed on the ~19 cards the channel had
  *  at subscribe time while the count above it climbed into the thousands.
  *
- *  Cost is bounded: the predicate fires only on a tick where the count actually moved, the poll
- *  itself pauses while the tab is unfocused, and a channel grid is normally a single 60-item page
- *  whose newest-first head the (older) backfilled videos don't disturb — so the refetch usually
- *  comes back structurally identical and re-renders nothing. */
+ *  What it costs, honestly: an invalidation refetches EVERY loaded page of the grid's infinite
+ *  query — one request per page the viewer has scrolled through, on each 4 s tick where the count
+ *  moved, for as long as the backfill runs (the poll pauses while the tab is hidden, and stops when
+ *  the back-catalogue is in). That is the right price, not an accident: backfilled videos are OLDER
+ *  than what the grid opened with, so under the newest-first order they land in the pages BELOW the
+ *  head — refreshing only the first page would leave out exactly the rows the backfill wrote. The
+ *  head itself comes back structurally identical and re-renders nothing. */
 export function useBackfillFeedRefresh(detail: ChannelDetail | undefined, qc: QueryClient) {
   const seen = useRef<ChannelDetail | undefined>(undefined);
   useEffect(() => {