The Streams standard has been updated to handle an edge case where ReadableStreamTee() would attempt to resolve the cancel() promise twice. While similar changes in the past have not resulted in user-visible changes (since implementations must already ignore resolving already-resolved promises), this particular case *does* lead to a behavior change (which is covered by new WPT tests). See https://github.com/whatwg/streams/pull/1118 for the specification change and https://github.com/web-platform-tests/wpt/pull/28266 for the new tests.
<rdar://problem/76286913>
Added test is passing, implementation works as expected.