fix: filter out future requests from query-clickhouse endpoint (#5398)

* fix: filter out future requests from query-clickhouse endpoint

When navigating to the request page from another page, some customers were
seeing requests with timestamps far in the future (e.g., August when current
date was October). This was caused by requests with incorrectly timestamped
data appearing at the top of results.

Added a filter `request_created_at <= now()` to both ClickHouse query
functions to exclude any requests with future timestamps:
- getRequestsClickhouseNoSort: used for created_at sorting
- getRequestsClickhouse: used for other sort types

Fixes ENG-3403

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat: add 1-minute buffer to future request filter

Co-authored-by: Justin Torre <chitalian@users.noreply.github.com>

---------

Co-authored-by: replicas-connector[bot] <replicas-connector[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: Justin Torre <chitalian@users.noreply.github.com>

Author: 4 people

valhalla/jawn/src/lib/stores/request/request.ts

@@ -171,11 +171,12 @@ export async function getRequestsClickhouseNoSort(
   const sortSQL = createdAtSort === "asc" ? "ASC" : "DESC";
   const query = `
     WITH top_requests AS (
-      SELECT 
+      SELECT
           request_id,
           request_created_at
       FROM request_response_rmt
       WHERE (${builtFilter.filter})
+        AND request_created_at <= now() + INTERVAL 1 MINUTE
       ORDER BY request_created_at ${sortSQL}
       LIMIT ${limit}
       OFFSET ${offset}
@@ -298,6 +299,7 @@ export async function getRequestsClickhouse(
     FROM request_response_rmt
     WHERE (
       (${builtFilter.filter})
+      AND request_created_at <= now() + INTERVAL 1 MINUTE
     )
     ${sortSQL !== undefined ? `ORDER BY ${sortSQL}` : ""}
     LIMIT ${limit}