PiP fixed probe + polygon return, suppress KNN warning, remove 12-node configs

[jathavaan]

Summary

• PiP workload uses 10 mixed probes; methodology says "fixed query point" #303 PiP queries return COUNT(*) instead of containing polygons #304: PiP entrypoints now use a single fixed query point (POINT_IN_POLYGON_PROBE_WGS84) and return actual polygon rows (SELECT *) instead of COUNT(*). result_cardinality and bytes_received metrics now carry correct meaning per §4.3.2.
• Suppress geographic CRS distance warning in knn_search_local #295: Suppress geographic CRS UserWarning in knn_search_local with scoped warnings.catch_warnings(). Distance semantics unchanged.
• Reduce databricks runs #341: Remove stale 12-node Databricks module references from DI wiring + earlier batch/ceiling work.

Closes #303
Closes #304
Closes #295

Test plan

• Run point-in-polygon-lookup-duckdb-small — verify returns polygon rows, not counts
• Run point-in-polygon-lookup-postgis-small — same
• Run point-in-polygon-lookup-local-small — returns GeoDataFrame
• Run knn-search-local-small — no UserWarning in logs
• Verify result_cardinality in output reflects actual polygon count

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.