fix(migrate): make 0002 timings column add idempotent

The previous deploy of c4f6cc1 failed because I had applied the timings
column manually via psql before the deploy ran, leaving the hash-based
migrate runner with raw ADD COLUMN that conflicts with the existing column.
Hash differs after this change so the runner will retry on next deploy
and succeed (no-op on the already-applied column, success path records
the hash).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/api/drizzle/0002_boring_the_stranger.sql

@@ -1 +1 @@
-ALTER TABLE "query_logs" ADD COLUMN "timings" jsonb;
+ALTER TABLE "query_logs" ADD COLUMN IF NOT EXISTS "timings" jsonb;