Advance Readable[Symbol.asyncIterator] out of experimental

[rektide]

Is your feature request related to a problem? Please describe.
I'm loving the use of asyncIteration provided by #17755 . It just works for me!

Unfortunately I can't work with this feature with my team, because when I use this feature, Node outputs:

ExperimentalWarning: Readable[Symbol.asyncIterator] is an experimental feature. This feature could change at any time

Getting ReadableStreams from experimental to something more stable would greatly advance #15709!

Describe the solution you'd like

Advancing Readable#[Symbol.asyncIterator] out of experimental would help me be able to deploy & use this awesome feature.

I'm also not sure what the criteria are for advancing this awesome feature into an unstable or stable state, where it no longer logs out on use. I've found a variety of tickets such as #23042 and #23785 that have landed improvements, which is great, but I'm not sure what we're looking for to advance this great feature's stability. My end user perspective is that the API is correct, and has been validated, across the past 6 months, and I'm hoping this ticket might serve to clarify what else we need or want to advance this feature.

Describe alternatives you've considered

No alternatives! Only forward! ;) Sorry, just having fun.

From a process perspective, we might possibly close this issue & continue working on this topic in #17755 , perhaps? It would be convenient for me to have an issue to track & follow for stabilization, so I know when this feature advances. But I'm not sure how experimental features are normally advanced through node. I'd love to know more about how Node handles advancing experimental features.

Thanks all.

[cjihrig]

I believe this was closed by #26989.