Restore TypeScript type checking during builds

[javierpr0]

Summary

next.config.ts disabled build-time type checking through typescript.ignoreBuildErrors: true. With that flag set, next build skips type validation entirely, so type errors can be merged and deployed without anything failing. This removes the flag and fixes the two pre-existing type errors it was masking.

Changes

• next.config.ts — remove typescript.ignoreBuildErrors. next build now fails on type errors instead of ignoring them.
• src/app/page.tsx — <OsintPanel> was receiving theme and setTheme, props the component neither declares nor uses, so they were silently discarded. Removed them from the call site. LayerPanel, which does accept those props, is left unchanged.
• src/lib/sdk/PolybolosClient.ts — the toGeoJSON return type referenced the UMD global GeoJSON.FeatureCollection, which TypeScript does not expose inside an ES module (it only resolved because the build never type-checked). Replaced it with an explicit import type { FeatureCollection } from "geojson".
• package.json / package-lock.json — add @types/geojson as a direct devDependency. It was already in the dependency tree transitively via maplibre-gl; promoting it to a direct dependency makes the type import resolvable and keeps the build reproducible.

Rationale

Turning off type checking at build time removes the main guarantee TypeScript provides in CI: prop, type, and API-contract regressions ship without warning. The two errors uncovered here are concrete proof the flag was hiding real problems — an unused prop pair and a type reference that only compiled because nothing validated it.

Verification

• npx tsc --noEmit — 0 errors
• next build — compiles successfully, all 42 routes generated

No runtime behavior changes: the removed props were already ignored by the receiving component, and the PolybolosClient change is type-only.

[vercel]

@javierpr0 is attempting to deploy a commit to the Amanda's projects Team on Vercel.

A member of the Team first needs to authorize it.