Beat schedule fix

[fcollman]

making beat schedule loading more robust

---

Note

Ensure Celery beat schedules load reliably by handling BEAT_SCHEDULES/beat_schedules, restoring config after updates, and adding targeted debug logs.

• Celery worker (materializationengine/celery_worker.py):
  • Initialize beat_schedules from app.config['BEAT_SCHEDULES'] and set celery.conf['beat_schedules'].
  • After celery.conf.update(app.config), restore beat_schedules from BEAT_SCHEDULES if missing; verify via debug logs.
  • In setup_periodic_tasks, fallback from celery.conf['beat_schedules'] to celery.conf['BEAT_SCHEDULES'] and normalize to beat_schedules.
  • Add debug logs detailing schedules content/type/length; broaden Celery logger level configuration.
• App config (materializationengine/config.py):
  • Log BEAT_SCHEDULES before/after config.cfg load (including type/length) to trace overwrites; maintain logger setup.

^{Written by Cursor Bugbot for commit 47d04d2. This will update automatically on new commits. Configure here.}