Define custom Dagster AutomationCondition logic to combine cron scheduling with eager upstream propagation

Steps

1. Set an asset's automation_condition to AutomationCondition.eager() to auto-materialize it whenever any of its upstream dependencies update.
2. Alternatively use AutomationCondition.on_cron(<schedule>) to materialize an asset once per schedule tick, after all upstream dependencies have updated.
3. Compose custom conditions using the AutomationCondition builder API to, for example, run on a fixed cadence OR whenever a dependency updates, while excluding runs where a dependency is missing or still in progress.
4. Attach the composed condition to the asset definition and ensure the automation sensor/daemon that evaluates automation conditions is enabled in your deployment.
5. Observe the asset's materialization history in the Dagster UI to confirm the condition triggers runs at the expected cadence and reacts correctly to upstream freshness.