feat(inspector): rebuild on devframe - #5276

The new `@unocss/inspector/devframe` subpath had no node10 type
resolution, failing `attw` in CI (publint/attw run only when CI=true).
Mirror the `typesVersions` wildcard map used across the monorepo.

A cold deploy build could race on a lazily-loaded language
("Language `html` not found"), failing the Netlify docs deploy
intermittently. Preload the grammars the twoslash transformers rely on.

Register `@devframes/service-shiki` on the definition (declared lazily by
package name, so the host imports it from the inspector's deps and merges
languages with any host-provided instance). Read-only CSS output panes now
render server-highlighted dual-theme HTML through the service via a new
`ShikiCode` component, degrading to plain text when the service is absent
(e.g. static builds). The editable REPL input and matched-token source
views keep CodeMirror.

`dev:client` served the SPA with no RPC backend, so it sat forever on
"Connection lost — reconnecting". Start a standalone devframe backend
(auth-less, single-user localhost) alongside it, scanning the inspector's
own sources for something to inspect. The client connects to it directly
over an absolute URL with the connection descriptor injected — Vite's proxy
mangles devframe's WebSocket frames and breaks its SSE session correlation,
so a direct cross-origin connection is used instead. Guarded on globalThis
so Vite reloads reuse the one instance, and degrades gracefully (with a hint
to build first) when the package's dist isn't available.

The sidebar hid a tree group that had only root-level files (no nested
folders), and the vanilla examples kept all their markup in `index.html`
plus plain `.ts` modules — which UnoCSS skips by default — so only one
module was ever tracked. Render a group when it has files OR folders, give
the examples a small multi-file `src/` structure, and opt their `.ts`
modules into the content pipeline so the tree reflects the whole app (like
the Next.js example, whose standalone scan already covers every file).

Replace the custom server broadcasts + typed client-function augmentation +
client event hooks + reconnect-refetch wiring with a single devframe shared
state ('changes'): the server bumps a revision, the client watches it to
refetch. A reconnecting client gets the latest snapshot for free, so stale
data self-heals without bespoke reconnection plumbing — less code and a
smaller maintenance surface.

The standalone /__unocss/ RPC bridge inherited devframe's loopback-only WS
origin check, so the upgrade was refused (403) whenever the dev server is
reached at a non-loopback origin — `vite --host`, containers, WSL, tunnels —
leaving the inspector stuck on "Connecting…". `devframeViteBridge` exposes no
way to override it, so mount the RPC backend via `initDevframe` directly with
`allowedOrigins: false`. The endpoint is served same-origin by the dev server
and the one-time-code gate is the real trust boundary, so the origin check
added nothing here.

Swap the sidebar file icons to the catppuccin set (per @antfu/design's
DisplayFileIcon), rendered through an `icon-catppuccin` shortcut that
inverts/rehues/dims the dark-tuned glyphs on a light surface and cancels back
to native color under `.dark` — so contrast tracks the color mode with no JS.

Upgrade the devframe family to 0.9.11 (devtools-kit 0.7.1), which adds the
`allowedOrigins` option to `devframeViteBridge` — the fix for the loopback-only
WS origin check reported upstream (devframes/devframe#348). Drop the inlined
`initDevframe` workaround and go back to the first-class bridge with
`allowedOrigins: false`, restoring the smaller integration.

Dropped during a branch sync; `attw` fails node10 resolution of
`@unocss/inspector/devframe` without it.