move requires_typed_event_stream and type_event_stream_error_message to op context

[jamiedemaria]

Summary & Motivation

Moves required_typed_event_stream and type_event_stream_error_message and associated properties and functions to OpExecutionContext instead of StepContext. This will help later up in the stack for making the OpExecutionContext and RunlessOpExecutionContext more similar

How I Tested These Changes

[jamiedemaria]

Current dependencies on/for this PR:

• master
  • PR move requires_typed_event_stream and type_event_stream_error_message to op context #18521 👈
    • PR Only have one kind of context for direct invocation #17554
      • PR deprecate methods on AssetExecutionContext that can be found via the DagsterRun object #17339
        • PR Direct invocation asset execution context #18549
          • 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.

[smackesey]

For the record, the reason requires_typed_event_stream was on StepExecutionContext is that at the time it was added, it was used in places where there was no access to OpExecutionContext. That's apparently no longer true, so it can be moved down.

[jamiedemaria]

closing, since moving these isn't required for the basic changes to get the context stack merged. We may need to do this move in the future when the asset context is no longer a subclass of op context, but we will figure that out at a later date