autopkgtest regressions against libuv1.44.2

There are two autopkgtest regressions in 16.14.2+dfsg1-1ubuntu3 when compiled against libuv1.44.2:

```
not ok 2053 parallel/test-socket-write-after-fin-error
  ---
  duration_ms: 0.518
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^

    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

      assert(gotServerError)

        at process.<anonymous> (/tmp/autopkgtest.0qinFV/build.3Ks/src/test/parallel/test-socket-write-after-fin-error.js:52:5)
        at process.emit (node:events:538:35) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
  ...

not ok 2485 parallel/test-tls-streamwrap-buffersize
  ---
  duration_ms: 0.412
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
        at Proxy.mustCall (/tmp/autopkgtest.0qinFV/build.3Ks/src/test/common/index.js:343:10)
        at TLSSocket.<anonymous> (/tmp/autopkgtest.0qinFV/build.3Ks/src/test/parallel/test-tls-streamwrap-buffersize.js:63:35)
        at TLSSocket.<anonymous> (/tmp/autopkgtest.0qinFV/build.3Ks/src/test/common/index.js:385:15)
        at Object.onceWrapper (node:events:645:28)
        at TLSSocket.emit (node:events:526:28)
        at TLSSocket.onConnectSecure (node:_tls_wrap:1563:10)
        at TLSSocket.emit (node:events:526:28)
        at TLSSocket._finishInit (node:_tls_wrap:944:8)
        at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12)
  ...
```

There has been considerable upstream discussion about this[1], and there is a patch available for the test-tls-streamwrap-buffersize failure, but not the other.

[1] https://github.com/nodejs/node/pull/42340