feat(example): add the Native List Row Style page

[huhuanming]

Stacked on #110 → #109 → #107. This PR's diff is P3 only.

What

The Native List Row Style example page, plus a DESIGN.md → STYLE_SPEC.md link.

Why this instead of listStyle

P3 was planned as list chrome (listStyle) plus an example page. I did the example page and deferred the chrome API, for two reasons:

1. Most chrome cannot be honored natively. Pull to refresh is a system control on both platforms (UIRefreshControl, SwipeRefreshLayout); the section index rail is three independent constant sets; the reorder count badge is drawn on Canvas inside Android's dispatchDraw. A unified API over that would declare knobs that silently do nothing on some platforms — the opposite of what the spec is for.
2. The native row style from feat(native-list): apply the row style on iOS and Android #110 is not device-verified yet. Stacking more unverified native changes on top makes any regression harder to localize.

So P3 delivers the thing that actually unblocks verification.

The page is a regression check, not a gallery

Every template renders twice — plain, then styled — behind a toggle. With the toggle off, the page must match the build from before the row style existed. Unstyled rows must not move by a pixel; that is the single most important thing to confirm on device.

The styled rows deliberately target what the field-to-view mapping is most likely to get wrong:

Row	What it proves
metricCard	style.value must hit the large number and style.title the small label, even though they share views with identity's title and subtitle
message	style.body and style.time reach the subtitle and status views
identity	A named token ($bodyMd), a raw override, badge, value, plus horizontalPadding and lineGap
rail, action	Slots that sit outside the main text column
explicit height	Text grown with $headingMd and an explicit height, because heights are not derived from the style (§6.1)

Verification

• The page typechecks cleanly against the worktree package source. The example app resolves @onekeyfe/react-native-native-list through a workspace symlink whose types point at an unbuilt lib/, so every NativeList page in the example already fails with TS2307 — pre-existing, 12 files. I verified this page with a throwaway tsconfig mapping the import to src/index.ts; 0 errors, and the temp file is not committed.
• eslint on the new page and route.tsx — clean.
• The example app's own tsc --noEmit has 72 pre-existing errors on main-equivalent code and is not a usable gate.

What to check on device

1. Open Native List Row Style, toggle the style off, and compare against a build without this stack — every row should be identical.
2. Toggle on: confirm the metricCard large number grows and turns green while its small label shrinks — if those two swap, the mapping is wrong.
3. Confirm no row clips its text, and that scrolling fast does not leak a font size into a neighbouring row (the recycling reset from feat(native-list): apply the row style on iOS and Android #110).

🤖 Generated with Claude Code

[originalix]

P2: [The regression page does not cover every styled row template]

When this page is used as the documented cross-platform regression check, buildRows only creates styled counterparts for identity, metricCard, message, rail, and action. The NativeList model also exposes style surfaces for activity, dataRow, market, mediaTile, sectionHeader, system, and walletGroup, so regressions in those binders are never rendered or exercised by the toggle.

Please add representative plain/styled pairs for the missing templates (including a styled section header) and have the toggle remove each counterpart’s style object, so the page actually covers the promised all-template comparison.