[v13.x backport] stream: don't destroy final readable stream in pipeline

[ronag]

If the last stream in a pipeline is still usable/readable
don't destroy it to allow further composition.

Fixes: #32105
Refs: #32110

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[ronag]

Note that the base PR (#32110) has NOT landed yet. I'm just preparing this in order to fast track. I'm not sure what the procedure here is and whether this can land first.

[ronag]

@szmarczak

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/29587/

[szmarczak]

LGTM

[mcollina]

lgtm

[szmarczak]

There may be an edge case where the source is an IncomingMessage, and in that case the connection will be destroyed after the response has gracefully ended. This will cause to create new connection every time you make a new request. But that should be fixed in

https://github.com/nodejs/node/blob/master/lib/_http_incoming.js#L121-L124

As it should destroy the socket only if the options.agent is set to false or options.createConnection is present.

This PR is good to merge IMO.

[ronag]

FYA: @MylesBorins@codebytere

[ronag]

@nodejs/streams PTAL, this PR (and #32110) needs another approval and should preferably land as soon as possible as it is affecting the ecosystem.

[MylesBorins]

landed in 4640ea2

@ronag fwiw backport prs technically don't require any sign off, although it is likely prudent to get someone to look at it. With matteo having signed off I think this is good enough