Feat: Geo Grid Maps Rank Tracking

[Pallavikumarimdb]

Description

Implements the Geo Grid Maps Rank Tracking feature, allowing local businesses to monitor organic positions across a coordinate grid.

Key Changes

• Database Schema: Added tables for configs, keywords, runs, and snapshots in both SQLite and Postgres.
• Backend Service & Repository: Implemented coordinate offset math, trigger logic, and developer mock-data simulation fallbacks.
• Server Functions: Created type-safe TanStack server functions validating project scope input.
• Frontend Dashboard: Added sidebar navigation, routing, a configuration setup wizard with presets, and an interactive colored grid map with local search metrics (ARP, SoLV).

Closes: #60

[Pallavikumarimdb]

Scope note: this PR is v1 of the full geo-grid rank tracking feature

This PR implements the core geo-grid pipeline config → scheduled/manual run → per-cell DataForSEO Maps SERP → color-coded grid + ARP/SoLV metrics

This also directly implements the "geographic rank grids" feature proposed by SKoess in Discord. To avoid duplicate work, I wanted to lay out the full scope here so it's clear this PR is the foundation, not the finished feature.

Already included in this PR:

• Grid configuration (center point, 3/5/7 grid, spacing), keyword CRUD, run trigger, and polling
• Real DataForSEO Maps SERP calls (with mock fallback for the default key)
• Color-coded grid UI with ARP and Share of Local Voice metrics

Planned follow-up work (out of scope for this PR):

• Device selection (desktop/mobile/both) - currently hardcoded to desktop
• Maps vs. Local Pack (local_finder) surface selection
• Business identification by Google Place ID/CID instead of name matching
• Scheduled runs wired into cron (scheduleInterval is currently a no-op column)
• Run-cost estimate and billing guard before triggering a live scan
• Competitor tracking, ratings/review counts, and run-over-run comparisons
• Interactive map rendering (currently a CSS grid) and custom/geocoded coverage areas
• Config edit/delete, per-cell run states, MCP exposure, and additional test coverage

I've already drafted the architecture for the remaining pieces (data model, service pipeline, and phased rollout) and plan to split it into follow-up issues after this PR lands. I'm noting it here so the overall feature scope is documented as one continuous effort rather than being re-proposed or split across parallel work.