[core-api][experimental] direct resource passing

[OwenKephart]

Summary & Motivation

decision: experimental -> public (could be convinced otherwise)
reason: this has existed for a long time, and even if it isn't directly recommended in most cases at the moment, we're moving to a world where more locally-scoped resource definitions are the norm and so this seems fair to support.
docs exist: api only

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

[OwenKephart]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [core-api][deprecated] Confirm all simple deprecations #26712
• [core-api][experimental] include_sources -> include_external_assets #26710
• [core-api][experimental] repository_def in RunStatusSensorDefinition #26709
• [core-api][experimental] allow_nonexistent_upstream_partitions #26708
• [core-api][experimental] observable_source_asset, multi_observable_source_asset #26706
• [core-api][experimental] Definitions.get_all_asset_specs, Definitions.with_reconstruction_metadata #26705
• [core-api][experimental] execution type #26695
• [core-api][experimental] freshness_policy param #26702
• [core-api][experimental] custom_path_fs_io_manager #26679
• [core-api][experimental] Definitions.merge #26704
• [core-api][experimental] create_repository_using_definitions_args #26703
• [core-api][experimental] DataVersion assorted APIs #26698
• [core-api][experimental] AssetSelection.tag #26697
• [core-api][experimental] Table metadata #26692
• [core-api][experimental] BackfillPolicy #26694
• [core-api][experimental][PLACEHOLDER] create beta decorator #26691
• [core-api][experimental] direct resource passing #26688 👈 (View in Graphite)
• [core-api][experimental] multi partition mappings #26686
• [core-api][experimental] AMP #26685
• [core-api][experimental] get_asset_provenance #26684
• [core-api] base #26770 : 1 other dependent PR (#26707 )
• master

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

[yuhan]

adding @dpeng817 to this one. i'm a little indifferent to GA vs not, so want second opinions here.

if we do end up making it public, i think we'll need to add docstring for resource_defs and io_manager_defs. not seeing them currently

[dpeng817]

I actually disagree with this.

I don't think we document direct resource passing anywhere outside of api docs, and it has known problems (specifically key collisions). There might be a few places we use it internally, but in general I think it doesn't fit with how the framework has evolved (you specify resources at the op level but assets at the spec level).

I think if we wanted to make it truly public we would at the very least need to resolve the key collisions problem (having scoped resources be a true concept within dagster) but that's unlikely to be prioritized any time soon.