fix(db): bump 0012/0013 journal timestamps so drizzle applies them

Same regression we hit with 0010/0011 in commit 1b7f553: drizzle's
migrator skips entries whose 'when' is older than the latest applied
migration's recorded created_at. 0012's when (1778412502601) and
0013's when (1778418181504) were generated BEFORE 0011's manually-
bumped when of 1778464002000, so 'pnpm migrate' kept reporting
'Migrations applied.' while silently skipping both. Result: web
500'd on every authenticated request — getCurrentUser hit
'column "email" does not exist' because the operators schema in
code expected the column 0013 was supposed to add.

Bumped 0012 to 0011.when + 1s and 0013 to + 2s, re-ran migrate.
operators now has the email column, reminders.delivery_window_end_hour
default is now 24 (the off-sentinel), and the web container is back
up with no 500s.

Note for future: the journal timestamps must be strictly monotonic
across the entries[] order. The fix in commit 1b7f553 didn't future-
proof us against the next batch. Keeping a long-term automated guard
against this is a TODO.

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

packages/db/migrations/meta/_journal.json

@@ -89,14 +89,14 @@
 		{
 			"idx": 12,
 			"version": "7",
-      "when": 1778412502601,
+			"when": 1778464003000,
 			"tag": "0012_lucky_masked_marvel",
 			"breakpoints": true
 		},
 		{
 			"idx": 13,
 			"version": "7",
-      "when": 1778418181504,
+			"when": 1778464004000,
 			"tag": "0013_tricky_yellowjacket",
 			"breakpoints": true
 		}