Bootstrap Beam scheduler environment

[fmercurio]

Summary

• bootstrap Beam's .env.example fallback before starting schedule:work
• extend CapRover definition validation to prevent this regression

Root cause

The Beam web entrypoint copies .env.example to .env before PHP-FPM starts. The scheduler overrides the image CMD and skipped that initialization. Laravel therefore used its MySQL fallback database forge, while the staging database is beam.

A temporary internal diagnostic job proved:

• Journal returned all three synthetic article IDs
• persistence then failed with SQLSTATE[HY000] [1049] Unknown database 'forge'

Runtime CapRover env variables still override fallback values; secrets remain injected at runtime.

Validation

• python3 caprover/scripts/validate-definitions.py
• git diff --check