RFC: Add a serializable argument class in preparation for invocation across a process boundary

[schrockn]

Summary & Motivation

Preparing for user-space execution of AMP rules. This separates arguments into ones that might be serialized by the daemon and passed to user space. The other arguments (e.g. AssetGraphView) can be reconstructed in the user process

How I Tested These Changes

BK

[schrockn]

• RFC: Add a serializable argument class in preparation for invocation across a process boundary #21928 : 2 dependent PRs (#21929 , #21992 ) 👈
• Just making the some of the names on AssetConditionEvalator not specific to AMP #21927 : 1 other dependent PR (#21938 )
• Disallow legacy access in SchedulingCondiitions #21925 : 1 other dependent PR (#21926 )
• Remove legacy context access in ParentNewerCondition #21924
• Extract materializable_in_same_run out of LegacyRuleEvaluationContext and call it directly from scheduling condition #21923
• Add long but public access to we can get instance queryer instance off of AssetGraphView #21922
• Create NonAGVInstanceInterface to avoid accessing legacy_context directly in SchedulingContext #21921
• SchedulingContext named tuple instead of DagsterModel #21919
• Eliminate legacy_context reference in RuleCondition #21918
• Delete the _queryer_ property from SchedulingContext` #21917
• master

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

Join @schrockn and the rest of your teammates on Graphite