Restore Geoapify provider setup and routing

[stef-k]

Summary

• make geocoding and directions provider choices save and survive reloads
• accept bounded Geoapify route snapping and documented step/metric semantics in the shared verification, Trip, and Mobile routing parser
• place validation messages at page scope instead of under Mapbox consent
• prepare backend v1.9.7

Production evidence

• bounded live Geoapify routing, reverse-geocoding, and autocomplete responses passed the production parsers
• mounted authenticated settings flow verified both capabilities, saved both Geoapify choices, and retained both choices after reload
• the temporary credential, responses, probe, and trace were deleted and were never committed

Validation

• release helper passed for v1.9.7
• focused provider/version tests passed
• build passed with zero warnings/errors
• LOC and diff checks passed

Screenshot

The user supplied screenshots capture the v1.9.6 regression. The corrected mounted flow was exercised directly; no credential-bearing trace or screenshot was retained.