Simplify return types of static constructors for AutomationCondition

[OwenKephart]

Summary & Motivation

As title. These return types were overly-specific. We have some subclasses that support additional methods, but most do not. To keep things more comprehensible for users that are seeing these types, use the least specific type possible in these cases.

How I Tested These Changes

Changelog

NOCHANGELOG

[OwenKephart]

• [1.9] Replace Auto-materialize references in the UI with Automation condition #25414
• [1.9] Update evaluation id logic to be in sync with tick ids #25269
• [1.9] Add automation_condition to observable_source_asset #25344
• [1.9] Create default_automation_condition_sensor in Definitions object #25201
• [1.9] Update deprecation warnings for automation_condition, auto_materialize_policy, and freshness_policy #25208
• [1.9] Remove experimental warnings from AutomationCondition static constructors #25207
• [1.9] Promote hidden params to top-level args in AutomationConditionSensorDefinition #25206
• [1.9] Update default value of allow_backfills to True #25204
• Add executed_with_root_target condition to handle partial runs / failures #25253
• Add error for user code sensors with too many entities targeted #25215
• Add test demonstrating that we do not hit the RESOURCE_EXHAUSTED error above a given threshold #25214
• Propagate automation condition information through the UI for user code conditions #25211
• Export AutomationContext and AutomationResult #25210
• Store allow_backfills in the sensor metadata #25203
• Create backfill_in_progress AutomationCondition #25190
• [refactor] Move all operands into a single file #25187
• Remove description property, make names more descriptive #25186
• Simplify return types of static constructors for AutomationCondition #25184 👈
• Add all_deps_blocking_checks_passed condition #25171
• Make existing conditions work with Asset Checks #25170
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @OwenKephart and the rest of your teammates on Graphite

[schrockn]

This gives us more option value so I think this is fine.

Note that I don't think the primary benefit here is simplicity but flexibility in implemenation. We could theorectically change the class of returned things without changing the type signature. There is a definite downside as it hides information from the user.

[OwenKephart]

Merge activity

• Oct 15, 3:52 PM EDT: A user started a stack merge that includes this pull request via Graphite.
• Oct 15, 3:53 PM EDT: Graphite rebased this pull request as part of a merge.
• Oct 15, 3:54 PM EDT: A user merged this pull request with Graphite.