v33

Drop baked block tables — live device data only, fail loud not stale

Per design pushback: a fallback snapshot can't add value (the controller is
useless without the Prime online) but CAN mask a real failure — after a firmware
reorder it would resolve to the wrong blocks silently. Stale data is more
dangerous than a visible failure.

- Remove MODULE_NAME[272] / MODULE_CATEGORY[272] / moduleCategory() from
  BlockCatalog.h. It now holds only our taxonomy (BlockCat enum), the live
  category-string -> generic map, and the param-candidate conventions — none of
  which are device snapshots.
- moduleName() is runtime-only (empty until the device list loads); resolveCat()
  no longer falls back to a baked category and does not cache transient
  categoryOfBlock failures (so a hiccup retries instead of sticking).
- Resolution requires the live list: if loadModuleTypes() hasn't succeeded,
  resolveLayoutForRig defers (keeps the spinner) and the net loop retries every
  1.5s, so a recovered link self-heals. Long-press still escapes to the Board
  Menu. Persistent spinner + connection bars make a real problem visible.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>