test: fix flaky test-http2-close-while-writing

The test was flaky due to a race condition where `client.close()` would
wait for a graceful shutdown while the server had already destroyed the
session/stream, leading to a timeout.

Changes:
- Replace `client.close()` with `client.destroy()` in the `close` event
  handler of the client stream.
- Add `common.mustNotCall()` error handlers to the client, client stream,
  and server session to catch unexpected errors.
- Add check `if (!client_stream.destroyed)` before destroying client
  stream in the server's data handler.

Refs: #33156

Author: Han5991

test/parallel/test-http2-close-while-writing.js

@@ -22,11 +22,16 @@ const server = http2.createSecureServer({
 let client_stream;
 
 server.on('session', common.mustCall(function(session) {
+  session.on('error', common.mustNotCall());
   session.on('stream', common.mustCall(function(stream) {
     stream.resume();
     stream.on('data', function() {
       this.write(Buffer.alloc(1));
-      process.nextTick(() => client_stream.destroy());
+      process.nextTick(() => {
+        if (!client_stream.destroyed) {
+          client_stream.destroy();
+        }
+      });
     });
   }));
 }));
@@ -36,9 +41,11 @@ server.listen(0, common.mustCall(() => {
     ca,
     maxSessionMemory: 1000
   });
+  client.on('error', common.mustNotCall());
   client_stream = client.request({ ':method': 'POST' });
+  client_stream.on('error', common.mustNotCall());
   client_stream.on('close', common.mustCall(() => {
-    client.close();
+    client.destroy();
     server.close();
   }));
   client_stream.resume();