fix: handle non-string query param types in resource registry

[Bortlesboat]

Problem

Numeric and boolean example values in queryParams (like page=1 or include_gt_community_data=true) get silently dropped from the Resource Registry display. Only string-typed values show up.

This happens because expandFields in schema.ts only handles string and object raw values -- raw number and boolean primitives fall through to the typeof raw !== 'object' guard and get skipped.

Reported in #623 with CoinGecko trending pools as an example: out of 4 query params (page, duration, include_gt_community_data, include), only duration and include were displayed.

Changes

schema.ts

• Handle typeof raw === 'number' in expandFields -- infers integer vs number type, pre-fills default
• Handle typeof raw === 'boolean' -- sets type to boolean with ['true', 'false'] enum and pre-fills default
• Fix fieldDefault extraction to preserve non-string defaults (was typeof field.default === 'string', now field.default != null ? String(field.default))

form/index.tsx

• Fix nested <pre> inside <pre> in the response viewer -- JSON responses now use a <div> wrapper, plain text keeps <pre>

schema.test.ts (new)

• 6 tests covering numeric, boolean, float, mixed-type params, and non-string defaults

Test plan

• All 6 new tests pass via pnpm test:run
• No new TypeScript errors (tsc --noEmit clean for changed files)
• View a resource with mixed query param types (e.g. CoinGecko trending pools) -- all params should appear

Closes #623

[vercel]

@Bortlesboat is attempting to deploy a commit to the Merit Systems Team on Vercel.

A member of the Team first needs to authorize it.

[Bortlesboat]

Friendly ping, any blockers on this one?