perf(eap-items): Index-prune and dedupe sentry.timestamp range filters

[phacops]

EAP item queries carry two overlapping timestamp conditions: the mandatory time-range bound (on the raw timestamp column) and any client-supplied sentry.timestamp filter. The latter was emitted as CAST(timestamp, 'Float64'), which can't drive granule or partition pruning, so it degenerated into a per-row scan layered on top of the mandatory bound — showing up as one shard being consistently slow on skewed data.

Range filters compare the raw column

sentry.timestamp is a normalized column, and attribute_key_to_expression maps every normalized column to CAST(<col>, <type>). Since timestamp is in the primary key (organization_id, project_id, item_type, timestamp) and the partition key toMonday(timestamp), the CAST defeats pruning. Range comparisons (<, <=, >, >=) on sentry.timestamp are now rewritten to target the raw DateTime column:

-- before
(CAST(timestamp, 'Float64') AS `sentry.timestamp_TYPE_DOUBLE`) >= 1781040732

-- after
timestamp >= toDateTime('2026-06-09 21:32:12')

The column is second-resolution DateTime, so CAST(timestamp, 'Float64') already yields whole seconds — comparing against toDateTime(value) is equivalent for the integer unix-second values clients send. EQUALS/IN and SELECTing sentry.timestamp (which must still return a number) keep the CAST path.

Dedupe of identical conditions

The rewrite reuses the same canonical toDateTime('YYYY-MM-DD HH:MM:SS') form as the mandatory time-range bound, so a client filter whose bounds equal the request window becomes a byte-identical expression. treeify_or_and_conditions now drops structurally-identical conjuncts from the top-level WHERE AND (A AND A == A) before re-nesting, collapsing those duplicates. Distinct ranges are left untouched — the AND of them yields the tightest window — and the pass is a no-op (no rebuild) when there are no duplicates.

Nothing downstream dedupes conditions (the ClickHouse formatter joins AND args verbatim), so this is the only place the duplicate gets removed. Because every RPC endpoint calls treeify_or_and_conditions, they all get both the raw-column rewrite (shared filter path) and the dedupe.

Tests build the query AST via build_query and assert on the generated WHERE clause (no live ClickHouse needed): equal ranges collapse to one bound, different ranges keep both, and 3+ distinct bounds are all kept and never use a Float cast.