chore(deps): upgrade EQL and eql-bindings to 3.0.3

`CS_EQL_VERSION` eql-3.0.2 -> eql-3.0.3, and the `eql-bindings` crate
=3.0.1 -> =3.0.3.

EQL 3.0.3 carries `eql_v3.grouped_value` (CIP-3657, EQL PR 423), which the
GROUP BY rewrite emits. Until now that commit was red on a clean install —
the aggregate did not exist in 3.0.2 and had to be applied to the dev
database by hand to test. It is now installed by the release, so
`select::group_by` and `select::regression` pass with no local patching.

`eql-bindings` was pinned two releases behind the SQL at 3.0.1; 3.0.2 and
3.0.3 are both the same ts-rs serde-attribute warning fix, with the
emitted TS/JSON byte-identical, so the jump carries no behaviour change.
The proxy uses the crate only in its schema loader, to map v3 domains to
capabilities.

Integration suite unchanged at 323 passing / 81 failing, with nothing
newly failing or passing. Mapper 109 and proxy 117 unit tests green.

Stable-Commit-Id: q-67fwe28n0ab44t0zefphhnqd4p

Author: freshtonic

CHANGELOG.md

@@ -8,7 +8,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ### Changed
 
-- **EQL v3 (searchable encryption)**: Proxy now targets EQL v3. Encrypted columns are declared with self-configuring, typed `jsonb` domains (for example `eql_v3_text_search`, `eql_v3_integer_ord`, `eql_v3_json_search`) that encode both the scalar type and the column's searchable capabilities in the column type itself, replacing EQL v2's opaque `eql_v2_encrypted` composite type and its separate `eql_v2_configuration` table. The bundled `cipherstash-client` is upgraded to 0.42.0 and EQL to 3.0.2. Existing v2-encrypted data and schemas must be migrated to v3.
+- **EQL v3 (searchable encryption)**: Proxy now targets EQL v3. Encrypted columns are declared with self-configuring, typed `jsonb` domains (for example `eql_v3_text_search`, `eql_v3_integer_ord`, `eql_v3_json_search`) that encode both the scalar type and the column's searchable capabilities in the column type itself, replacing EQL v2's opaque `eql_v2_encrypted` composite type and its separate `eql_v2_configuration` table. The bundled `cipherstash-client` is upgraded to 0.42.0 and EQL to 3.0.3. Existing v2-encrypted data and schemas must be migrated to v3.
 
 ### Added
 

Cargo.lock

@@ -49,7 +49,7 @@ cts-common = { version = "=0.42.0" }
 # EQL v3 domain catalog: maps Postgres domain names to (token type, SEM terms).
 # The authoritative source for a column's domain identity (ADR-0002); only the
 # SchemaManager depends on it, keeping eql-mapper wire-format-agnostic.
-eql-bindings = { version = "=3.0.1" }
+eql-bindings = { version = "=3.0.3" }
 
 thiserror = "2.0.9"
 tokio = { version = "1.44.2", features = ["full"] }

Cargo.toml

@@ -34,7 +34,7 @@ CS_PROXY__HOST = "host.docker.internal"
 # Misc
 DOCKER_CLI_HINTS = "false" # Please don't show us What's Next.
 
-CS_EQL_VERSION = "eql-3.0.2"
+CS_EQL_VERSION = "eql-3.0.3"
 
 
 [tools]