chore: move cli/tests/ -> tests/ (#22369)

This looks like a massive PR, but it's only a move from cli/tests ->
tests, and updates of relative paths for files.

This is the first step towards aggregate all of the integration test
files under tests/, which will lead to a set of integration tests that
can run without the CLI binary being built.

While we could leave these tests under `cli`, it would require us to
keep a more complex directory structure for the various test runners. In
addition, we have a lot of complexity to ignore various test files in
the `cli` project itself (cargo publish exclusion rules, autotests =
false, etc).

And finally, the `tests/` folder will eventually house the `test_ffi`,
`test_napi` and other testing code, reducing the size of the root repo
directory.

For easier review, the extremely large and noisy "move" is in the first
commit (with no changes -- just a move), while the remainder of the
changes to actual files is in the second commit.

1 files changed, 0 insertions, 69 deletions

diff --git a/cli/tests/node_compat/test/parallel/test-stream-write-destroy.js b/cli/tests/node_compat/test/parallel/test-stream-write-destroy.js
deleted file mode 100644
index a4f103547..000000000
--- a/cli/tests/node_compat/test/parallel/test-stream-write-destroy.js
+++ /dev/null
@@ -1,69 +0,0 @@
-// deno-fmt-ignore-file
-// deno-lint-ignore-file
-
-// Copyright Joyent and Node contributors. All rights reserved. MIT license.
-// Taken from Node 18.12.1
-// This file is automatically generated by `tools/node_compat/setup.ts`. Do not modify this file manually.
-
-'use strict';
-require('../common');
-const assert = require('assert');
-const { Writable } = require('stream');
-
-// Test interaction between calling .destroy() on a writable and pending
-// writes.
-
-for (const withPendingData of [ false, true ]) {
-  for (const useEnd of [ false, true ]) {
-    const callbacks = [];
-
-    const w = new Writable({
-      write(data, enc, cb) {
-        callbacks.push(cb);
-      },
-      // Effectively disable the HWM to observe 'drain' events more easily.
-      highWaterMark: 1
-    });
-
-    let chunksWritten = 0;
-    let drains = 0;
-    w.on('drain', () => drains++);
-
-    function onWrite(err) {
-      if (err) {
-        assert.strictEqual(w.destroyed, true);
-        assert.strictEqual(err.code, 'ERR_STREAM_DESTROYED');
-      } else {
-        chunksWritten++;
-      }
-    }
-
-    w.write('abc', onWrite);
-    assert.strictEqual(chunksWritten, 0);
-    assert.strictEqual(drains, 0);
-    callbacks.shift()();
-    assert.strictEqual(chunksWritten, 1);
-    assert.strictEqual(drains, 1);
-
-    if (withPendingData) {
-      // Test 2 cases: There either is or is not data still in the write queue.
-      // (The second write will never actually get executed either way.)
-      w.write('def', onWrite);
-    }
-    if (useEnd) {
-      // Again, test 2 cases: Either we indicate that we want to end the
-      // writable or not.
-      w.end('ghi', onWrite);
-    } else {
-      w.write('ghi', onWrite);
-    }
-
-    assert.strictEqual(chunksWritten, 1);
-    w.destroy();
-    assert.strictEqual(chunksWritten, 1);
-    callbacks.shift()();
-    assert.strictEqual(chunksWritten, useEnd && !withPendingData ? 1 : 2);
-    assert.strictEqual(callbacks.length, 0);
-    assert.strictEqual(drains, 1);
-  }
-}