perf(NODE-5771): improve new connection

[nbbeeken]

Description

What is changing?

• Adds our own version of data event emitter -> asyncIterator helper
  • Notably changes from the standard library, removal of watermark functionality
  • Reduced the generic-ness to only work for data events and remove the need to destructure the value returned by the iterator
• Removes re-creating a AbortController per command
• Moves I/O helpers to class methods (to get Typescript privacy functionality)
• Creates promisified socketWrite helper once at the Connection construction
• Connects a transform stream to socket that buffers until message size is received
• Reworks abortable helper to not create a "done" signal, instead simplify the promise wrapping and abort listener removal to lower performance cost

Is there new documentation needed for these changes?

No.

What is the motivation for this change?

Improves the performance of the new connection layer to be on par with our existing connection layer. The major cost was constructing many AbortSignals, however, going back to using a stream to just collect chunks gets us within a margin of error of the old performance.

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[baileympearson]

nothing blocking since I'm OOO starting tomorrow, just some comments

[durran]

One question - did we also profile memory consumption?

[andreialecu]

Hey @nbbeeken @durran - not sure how to easily bring this to attention, but we discovered this issue: Automattic/mongoose#14877 and it seems to pin down to mongodb 6.4.0

6.3.0 is unaffected. There's a repro in the issue.