Update reject_pending_read_request and merge with releaseLock()

[MattiasBuelens]

Summary

Currently, we have a separate entry called reject_pending_read_request in both ReadableStreamDefaultReader and ReadableStreamBYOBReader (added in #16919) to show whether a browser has implemented the new behavior for releaseLock() specified in whatwg/streams#1168.

This PR merges that entry into the existing releaseLock() entry, marking the old behavior as a "partial implementation" instead. It also updates the compatibility data for the new behavior of releaseLock(). All major browsers now implement the new behavior.

Test results and supporting details

• Chrome added support in version 105. See the Chromium bug and the diff between Chrome 104 and 105 on wpt.fyi.
• Edge added support in version 105, mirroring Chrome. See the diff on wpt.fyi.
• Safari added support in version 17.0. See the Webkit bug and the diff between Safari 16.6 and 17.0 on wpt.fyi.
  • Note that Safari does not yet support ReadableStreamBYOBReader, so I only updated the data for ReadableStreamDefaultReader.
• Node.js added support in version 18.9.0. See the commit and the 18.9.0 changelog.
• Deno added support in version 1.18.0. See the commit and the 1.18.0 changelog.

[MattiasBuelens]

Alternatively, should we just remove this entry and merge it into the releaseLock() entry? The new behavior is now well standardized and widely adopted.

[skyclouds2001]

and need to add an entry to https://github.com/mdn/browser-compat-data/blob/main/browsers/nodejs.json

[MattiasBuelens]

I went ahead and removed the reject_pending_read_request entry, merging it into the existing releaseLock() entry. I think this better reflects that this behavior change only affects the releaseLock() method, and that older versions with the old behavior are only "partially" implementing the standard.

I believe this removal is warranted under the rules for removing irrelevant features, but I'm open to discuss. Maybe @hamishwillee could chime in, as they added the feature in the first place in #16919? 🙂