fix(ci): PR #281 — duckdb 1.10503.1 breaks spatial extension loading (version mismatch)

[evan-zhang11]

Problem

PR #281 bumps the cargo-minor-patch group with 12 updates, including duckdb from 1.10500.0 to 1.10503.1. This causes 3 CI check failures:

1. backend_tests — spatial extension version mismatch

duckdb crate version mismatch: Cargo.lock=1.10503.1, manifest=1.10500.0

All tests panic at db.rs:416 — Failed to install and load spatial extension.

2. backend_postgis_integration — all 6 tests fail

Same root cause: DuckDB spatial extension cannot be loaded with the newer duckdb crate version. Tests:

• test_postgis_empty_relation_registration_succeeds
• test_postgis_quoted_property_identifiers_and_aliases_work
• test_postgis_register_preview_publish_flow
• test_postgis_rejects_composite_unique_fid_index
• test_postgis_rejects_include_only_fid_index
• test_postgis_view_registration_succeeds

3. frontend_e2e — likely cascading failure from backend

Root Cause

The scripts/ci/check_spatial_extension_version.sh script checks that the Cargo.lock duckdb version matches the manifest version used to build/download the spatial extension. Bumping duckdb without updating the extension binary causes this mismatch.

Fix Options

1. Preferred: Update the spatial extension download/setup to match duckdb 1.10503.1
2. Quick fix: Revert the duckdb bump from this PR (keep at 1.10500.0) and handle it separately with proper extension updates

Other PRs

• PR chore(deps): bump rust from 1.95-slim-bookworm to 1.96-slim-bookworm #278 (rust 1.96) — ✅ all green
• PR chore(deps): bump the npm-minor-patch group in /frontend with 4 updates #279 (npm minor/patch) — ✅ all green
• PR chore(deps): bump i18next from 25.8.17 to 26.3.0 in /frontend #280 (i18next 26) — ✅ all green
• PR chore(deps): bump rusqlite from 0.39.0 to 0.40.0 #282 (rusqlite 0.40) — ✅ all green