Feat automation timezones catchup

[BelhsanHmida]

Description

• Store an IANA timezone for each forecast automation.
• Default new automations to FLEXMEASURES_TIMEZONE.
• Validate timezone names and expose the timezone through the CLI, API and UI.
• Persist a UTC scheduling cursor for each automation.
• Interpret cron expressions in the automation's timezone.
• Catch up missed forecast occurrences after runner downtime.
• Coalesce multiple missed occurrences into the most recent useful forecast.
• Handle daylight-saving transitions:
  • skipped local times run once after the spring-forward transition;
  • repeated local times run only once during the fall-back transition.
• Claim each scheduled occurrence before queueing while preserving the existing at-most-once failure policy.
• Add migration, documentation, changelog entries and regression coverage.
• Added changelog item in documentation/changelog.rst

Look & Feel

The automation CLI accepts an explicit timezone:

flexmeasures add automation \
  --asset-id 1 \
  --generator-id 2 \
  --recurrence "0 9 * * *" \
  --timezone Europe/Amsterdam

The automation UI and API now expose the configured timezone and persistent scheduling cursor.

How to test

Run the affected automation test modules:

pytest \
  flexmeasures/cli/tests/test_automations.py \
  flexmeasures/data/schemas/tests/test_automations.py \
  flexmeasures/data/tests/test_automation_scheduling_fresh_db.py \
  flexmeasures/data/tests/test_automations_fresh_db.py \
  flexmeasures/api/v3_0/tests/test_automations_api.py \
  flexmeasures/ui/tests/test_asset_crud.py

The regression coverage includes:

• Default and explicit IANA timezones.
• Invalid timezone rejection.
• Automations in different timezones.
• Normal due and non-due occurrences.
• Spring-forward and fall-back transitions.
• One or multiple missed occurrences.
• Persistent cursor behavior across runner restarts.
• Inactive automations.
• Duplicate prevention.
• Preservation of the existing failure guard.

Further Improvements

Durable execution records, partial-failure states and retry lifecycle management remain outside this PR and are tracked separately in #2393.

Catch-up behavior is intentionally limited to forecast automations. Policies for schedule and report automations should be defined separately.

Related Items

Closes #2392.

Built on the forecast automation work from #2290.

---

Sign-off

• I agree to contribute to the project under Apache 2 License.
• To the best of my knowledge, the proposed patch is not based on code under GPL or another incompatible license.

[read-the-docs-community]

Documentation build overview

📚 flexmeasures | 🛠️ Build #33923921 | 📁 Comparing 64b4b8e against latest (65d2a70)

  🔍 Preview build  

19 files changed · + 3 added · ± 16 modified

+ Added

• _autosummary/flexmeasures.data.models.automations.html
• _autosummary/flexmeasures.data.schemas.automations.html
• _autosummary/flexmeasures.data.services.automations.html

± Modified

• changelog.html
• genindex.html
• http-routingtable.html
• py-modindex.html
• _autosummary/flexmeasures.api.v3_0.assets.html
• _autosummary/flexmeasures.data.models.data_sources.html
• _autosummary/flexmeasures.data.models.html
• _autosummary/flexmeasures.data.queries.generic_assets.html
• _autosummary/flexmeasures.data.schemas.html
• _autosummary/flexmeasures.data.services.html
• and 6 more...