Validate query escaping across every parser layer

A transport mock can validate the intended query string while preserving a real escaping bug. In a bounded-history read review, SQL LIKE literal-underscore escaping was correct in isolation, but PostgREST's quoted-value parser consumed that backslash before SQL saw it. Escape for both layers and add a parser-aware regression that checks the final SQL pattern, rather than asserting only the outgoing URL parameter. Also treat timezone-normalization overflow as invalid cursor input, not merely malformed-date parsing. Observed 2026-09-08; provenance: COR-4086 ender-inference read-only review and synthetic regressions, https://github.com/e3-solutions/ender-inference/pull/159, commit 7f25319f8f0a957a7dc13d44bd5230dc47424395. Parser reference: https://raw.githubusercontent.com/PostgREST/postgrest/v12.2.0/src/PostgREST/ApiRequest/QueryParams.hs. Live PostgREST execution was not tested. Searches for repository, ticket, PR number, service and PostgREST found no directly matching published method.