Fix persisted worker bootstrap recovery query

[mrubens]

What changed

• move the persisted worker-bootstrap restart lookup to a dedicated core Drizzle query
• preserve the correlated task_run_events.run_id = task_runs.id reference
• add regression coverage that inspects the generated SQL and rejects the invalid relational alias

Why

The relational query builder aliased the outer task_runs table and remapped columns inside the correlated raw SQL fragment. That produced references such as taskRuns.run_id, taskRuns.source, and taskRuns.details, even though those columns belong to task_run_events. PostgreSQL rejected the recovery scan and interrupted controller iterations.

Impact

Controllers can scan for persisted bootstrap restarts without query failures, allowing queued work and bootstrap recovery to continue normally.

Validation

• full controller Vitest suite: 117 passed, 2 skipped
• controller and database TypeScript checks
• controller and database ESLint checks
• repository formatting check
• generated-SQL regression test
• corrected read-only correlation accepted by PostgreSQL

[roomote-roomote]

No code issues found. See task

_{Reviewed bc2bc51}