support Asset and Op ExecutionContexts in standard execution path

[jamiedemaria]

Summary & Motivation

This PR is not strictly required to merge #17339. However, as we deprecate more methods, we will begin to deprecate context methods that are called in the main execution pathway.

This PR proposes adding a subobject to both AssetExecutionContext and OpExecutionContext that contains all methods/properties that need to be accessed in the execution code path.

How I Tested These Changes

[jamiedemaria]

Current dependencies on/for this PR:

• master
  • PR Only have one kind of context for direct invocation #17554
    • PR duplicate op context methods on asset context  #18573
      • PR deprecate methods on AssetExecutionContext that can be found via the DagsterRun object #17339
        • PR Direct invocation asset execution context #18549
          • PR deprecate asset_partition_*_for_output on AssetExecutionContext #19436
            • PR [docs] remove asset_partition_*_for_output from docs #19437
              • PR deprecate op related methods from AssetExecutionContext #19441
          • PR Make upstream asset materialization events available on the context #18971
            • PR [wip] store the tags fetched by data versioning so we can use them for upath io manager #19324
              • PR [UPath I/O managers] special case handling of None outputs #18820
            • PR Make input partitions methods based on asset key not input name #19027
              • PR Support partitioned assets for fetching latest AssetMaterializations #19286
              • PR [do not merge] base example to showcase new apis #19199
                • PR [prototype] sub-context for each upstream dependency  #19283
                • PR [prototype] AssetExecutionContext partition methods on sub context #19236
                • PR [prototype] AssetExecutionContext partition methods given as named tuple #19037
                • PR [prototype] AssetExecutionContext partition methods directly on the context #19032
            • PR [wip] two execution contexts with minimal changes #18543
              • PR [wip] see wht needs to change when asset context is no longer an op context #18553
        • PR support Asset and Op ExecutionContexts in standard execution path #17972 👈
          • PR [wip] add AssetExecutionContext to direct invocation #18044

This stack of pull requests is managed by Graphite.

[github-actions]

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-ahy46vn8d-elementl.vercel.app
https://jamie-execution-path-with-two-contexts.core-storybook.dagster-docs.io

Built with commit e64fb39.
This pull request is being automatically deployed with vercel-action

[jamiedemaria]

having to pass the OpExecutionContext here is kind of annoying, but the alternative is doing isinstance(context, AssetExecutionContext) checks in the core execution code so that we can access context.op_execution_context when the context is an AssetExecutionContext

[jamiedemaria]

another option could be to move the functions needed from OpExecutionContext in the core execution path (has_events and consume_events) into the ExecutionProperties named tuple. I can look into that option as well. It might require passing the step execution context to this class, so might not be much better