Mark the baseline as applied on prod and staging

Prod and staging schemas already match schema.ts (push has kept them in sync), so the baseline migration must be recorded as applied there, not executed. Drizzle has no built-in "fake apply", the standard approach is inserting the journal row by hand.

• On each existing environment, insert the baseline row into __drizzle_migrations (hash + created_at matching the journal)
• Verify with drizzle-kit migrate: it should report nothing to do
• Fresh databases (local dev, CI) just run the migration normally
• Take a backup before touching prod, obviously