Fix generated calendar date filter semantics

[Dastari]

Summary

• render generated calendar predicates as sargable half-open ranges with exact inclusive-date behavior
• validate calendar spans, relative offsets, and required ordered Between bounds across GraphQL and programmatic query paths
• preserve SQL three-valued logic in SQLite spatial fallback evaluation, including NULL under AND, OR, and NOT
• publish the exact supported date-filter grammar through the semantic operation catalogue

Calendar clocks

• PostgreSQL uses the session CURRENT_DATE
• SQL Server uses the server-local date from GETDATE()
• SQLite uses UTC through date('now'); spatial fallback captures one UTC date for the query evaluation pass

A configurable application calendar/timezone seam and broader typed input normalization remain separate follow-up designs to avoid changing scalar contracts in this correction.

Release impact

• graphql-orm: 0.30.0
• graphql-orm-macros: 0.30.0
• graphql-orm-operation-catalog: 0.4.0
• graphql-orm-ai-tool-profiles remains 0.10.2 and passes its consumer tests
• root and fixture lockfiles contain only the aligned workspace package version changes

Verification

• full graphql-orm test suite, including deterministic date-boundary and SQLite fallback regressions
• operation-catalog and AI tool-profile tests
• PostgreSQL and SQL Server no-default-feature compile lanes
• warnings-denied Clippy and Rustdoc for changed packages
• documentation, workspace inventory, release-state, release-manifest, dependency-boundary, package-release-policy, and SemVer gates

Documentation impact

Updated the root and crate release notes, migration guide, installation versions, backend clock reference, macro/filter reference, and generated workspace inventory.

• Documentation updated
• No documentation impact