stream: fix deadlock when cloning webstreams

[tsctx]

Fixes #44985.
Fixed a problem where the process would not terminate if structuredClone was used for webstream and body was not consumed.

[nodejs-github-bot]

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

[aduh95]

Can you amend the commit message so it matches our guidelines? using is not an imperative verb, I suggest something like stream: fix deadlock when cloning webstreams

node/doc/contributing/pull-requests.md

Lines 170 to 172 in 1149d6b

	* be prefixed with the name of the changed [subsystem](#appendix-subsystems)
	and start with an imperative verb. Check the output of `git log --oneline
	files/you/changed` to find out what subsystems your changes touch.

[nodejs-github-bot]

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

[tsctx]

There seems to be a problem with FinalizationRegistry, so please wait for that to be resolved.

[nodejs-github-bot]

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

[H4ad]

@tsctx Can you elaborate? (just use request change to block merge)

[tsctx]

@H4ad
#49344
#47748

[jasnell]

Appreciate the work on this but this isn't the correct fix. The issue is the fact that cloned ReadableStream and WritableStream instances use a MessageChannel under the covers to communicate. The MessagePorts for each need to be unref'd in order to allow the process to exit. I'll have an alternative PR opened shortly.