stream: add regression test for async iteration completion

A test was missing for an async iterator created after the stream
had emitted 'close'. This was regressed by #31314.

See: #31314

PR-URL: #31508
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>

Author: mcollina

test/parallel/test-stream-readable-async-iterators.js

@@ -527,5 +527,24 @@ async function tests() {
   p.then(common.mustCall()).catch(common.mustNotCall());
 }
 
+{
+  // AsyncIterator should finish correctly if destroyed.
+
+  const r = new Readable({
+    objectMode: true,
+    read() {
+    }
+  });
+
+  r.destroy();
+  r.on('close', () => {
+    const it = r[Symbol.asyncIterator]();
+    const next = it.next();
+    next
+      .then(common.mustCall(({ done }) => assert.strictEqual(done, true)))
+      .catch(common.mustNotCall());
+  });
+}
+
 // To avoid missing some tests if a promise does not resolve
 tests().then(common.mustCall());