Move stream development out from core

[ronag]

Now that https://github.com/nodejs/readable-stream is up to date with the latest node version I would like to bring up the discussion of moving development of stream out of core in a similar way we currently do with undici.

[ronag]

@nodejs/streams @mcollina

[ronag]

In a practical sense this means:

• All new stream PR's should go to https://github.com/nodejs/readable-stream
• Core should include https://github.com/nodejs/readable-stream the same way as undici.

[ronag]

@targos I believe we might need your help to do this.

[targos]

Sure, on what front?

[ronag]

Sure, on what front?

Assuming there is consensus. Setting up the workflow with merging readable-streams into core similar to what we do with undici.

[mscdex]

What benefit would moving it out of core give us?

[ronag]

Easier to develop and easier to keep the ecosystem up to date. I believe @mcollina can better articulate the benefits.

[benjamingr]

I'm +0 on this

[jasnell]

I'd be +1 on this with the caveat that we need to continue to carefully deal with breaking changes in the streams API. So long as that continues to be a priority, I've no problems with moving this piece out.