ci: fix timezone and timeout for burn-in pipeline

[Trevor Jones (tjones60)]

Set the timezone so it starts at 7PM as intended instead of noon, and increase the timeout from the default of 6 hours to 15 hours.

[Copilot]

🟢 Approval recommended

The timezone and timeout changes are consistently wired through the Flowey pipeline types, YAML generation, and the regenerated workflow output.

Pull request overview

This PR fixes the Burn In GitHub Actions schedule to run at 7PM Pacific time as originally intended (rather than being interpreted in UTC), and increases the job timeout to accommodate the expected multi-hour runtime.

Changes:

• Add optional IANA timezone support to Flowey’s GhScheduleTriggers and propagate it into the generated GitHub Actions YAML.
• Configure the burn-in pipeline schedule to use America/Los_Angeles.
• Increase the burn-in workflow job timeout to 900 minutes (15 hours).

File summaries

File	Description
flowey/flowey_hvlite/src/pipelines/burn_in.rs	Sets the burn-in schedule timezone and increases pipeline job timeout.
flowey/flowey_core/src/pipeline.rs	Extends GhScheduleTriggers to include an optional timezone field.
flowey/flowey_cli/src/pipeline_resolver/github_yaml/mod.rs	Propagates the new timezone field into generated GitHub YAML schedule entries.
flowey/flowey_cli/src/pipeline_resolver/github_yaml/github_yaml_defs.rs	Adds timezone to the serialized Cron schema (omitted when None).
.github/workflows/openvmm-burn-in.yaml	Regenerated workflow reflecting the timezone and 15-hour timeout settings.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

3 Petri tests failed (0 unstable)