feat(jobs): configure OPTIMIZATION_JOBS_DB for Cloud Run deployment

[markboenigk]

Problem

The optimization jobs feature returns "Optimization jobs are not configured" in production because the OPTIMIZATION_JOBS_DB connection string environment variable is not set in the Cloud Run service.

The health endpoint confirms this:

"optimization_jobs_db": "missing",
"optimization_jobs_db_detail": "missing database connection string"

What's needed

1. Provision a database (Postgres or equivalent) for optimization jobs
2. Set the OPTIMIZATION_JOBS_DB connection string as a secret/env var in the Cloud Run service (infra/cloud-run/service.yaml)
3. Redeploy

Context

• The async optimization jobs API was introduced in feat: add async optimization jobs API #116
• The health probe no longer blocks on this being unconfigured (fixed in hotfix merged to main today), but the feature itself remains non-functional without the DB
• optimization_job_workers_expected and optimization_job_workers_healthy are both 0 in production

/cc @phongndo

[markboenigk]

Start Address: Best Western University Lodge, 123, B Street, Davis, Yolo County, California, 95616, United States
Tested locations:

• Davis Food Cooperative, 620, G Street, Downtown Davis, Central Davis, Davis, Yolo County, California, 95616, United States
• 1525, Tulip Lane, East Davis, Davis, Yolo County, California, 95618, United States
• Holmes Junior High School, 1220, Drexel Drive, East Davis, Davis, Yolo County, California, 95617, United States