Extract ASSET_TYPE_MAP into its own module; add Vitest + parser test suite

[ArneshBanerjee]

Summary

Two structural improvements, no behavior change to the running app:

1. refactor(types): Extract ASSET_TYPE_MAP and OPERATOR_ALIASES (~1000 lines of data) out of lib/types.ts into a new lib/asset-types.ts, with a shared AssetTypeConfig interface. lib/types.ts shrinks from 1079 → 54 lines and is now a pure types module. The constants are re-exported from lib/types.ts so existing imports still work; internal callers (parser.ts, overpass.ts) are updated to import from the new module directly.
2. test: Add Vitest as the test runner (npm test, npm run test:watch) and a 23-test suite for lib/parser.ts covering both structured (type: / operator: / region: / country: / near: / radius:) and natural-language queries, plus validateQuery error paths. Pins down current parser behavior so future refactors can be done safely.

Why

• lib/types.ts had grown into a giant data file; navigating types or adding a new asset type required scrolling past a thousand-line table. Splitting makes both files reviewable and lets the type-shape change independently of the data.
• There are no tests in the repo today; the parser is the single biggest place where regressions can sneak in unnoticed.

Notes for review

• I did not modify CI in this PR to avoid conflicting with PR Escape user operator input in Overpass queries; add typecheck and build to CI #9 (which already extends the workflow with typecheck/build). Once PR Escape user operator input in Overpass queries; add typecheck and build to CI #9 lands (or this one does — order doesn't matter), the test step (npm test) should be appended to the workflow. Happy to follow up with a tiny PR or rebase, whichever you prefer.
• While writing tests I noted two latent parser bugs worth flagging for a future PR: (a) the substring-based operator matcher classifies aws data centers in virginia as the vodafone operator because "virginia" contains "vi" (a vodafone alias); (b) the broad \btowers?\b regex can shadow more specific patterns depending on order. Both are out of scope here.
• I also audited lib/search-index.ts: it is not dead — it powers the autocomplete suggestions in SearchBar.tsx. It does maintain its own parallel asset-type list, which is a duplication worth consolidating later but is out of scope for this PR.

Test plan

• npm run lint — clean
• npx tsc --noEmit — clean
• npm test — 23/23 passing
• npm run build — clean
• Confirmed lib/types.ts still exports ASSET_TYPE_MAP, OPERATOR_ALIASES, and AssetTypeConfig for backward compatibility.

🤖 Generated with Claude Code

[vercel]

Someone is attempting to deploy a commit to the ni5arga's projects Team on Vercel.

A member of the Team first needs to authorize it.