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, 64 deletions

diff --git a/cli/tests/node_compat/test/parallel/test-stream-writableState-uncorked-bufferedRequestCount.js b/cli/tests/node_compat/test/parallel/test-stream-writableState-uncorked-bufferedRequestCount.js
deleted file mode 100644
index 0320d1a5d..000000000
--- a/cli/tests/node_compat/test/parallel/test-stream-writableState-uncorked-bufferedRequestCount.js
+++ /dev/null
@@ -1,64 +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';
-
-const common = require('../common');
-const assert = require('assert');
-const stream = require('stream');
-
-const writable = new stream.Writable();
-
-writable._writev = common.mustCall((chunks, cb) => {
-  assert.strictEqual(chunks.length, 2);
-  cb();
-}, 1);
-
-writable._write = common.mustCall((chunk, encoding, cb) => {
-  cb();
-}, 1);
-
-// first cork
-writable.cork();
-assert.strictEqual(writable._writableState.corked, 1);
-assert.strictEqual(writable._writableState.bufferedRequestCount, 0);
-
-// cork again
-writable.cork();
-assert.strictEqual(writable._writableState.corked, 2);
-
-// The first chunk is buffered
-writable.write('first chunk');
-assert.strictEqual(writable._writableState.bufferedRequestCount, 1);
-
-// First uncork does nothing
-writable.uncork();
-assert.strictEqual(writable._writableState.corked, 1);
-assert.strictEqual(writable._writableState.bufferedRequestCount, 1);
-
-process.nextTick(uncork);
-
-// The second chunk is buffered, because we uncork at the end of tick
-writable.write('second chunk');
-assert.strictEqual(writable._writableState.corked, 1);
-assert.strictEqual(writable._writableState.bufferedRequestCount, 2);
-
-function uncork() {
-  // Second uncork flushes the buffer
-  writable.uncork();
-  assert.strictEqual(writable._writableState.corked, 0);
-  assert.strictEqual(writable._writableState.bufferedRequestCount, 0);
-
-  // Verify that end() uncorks correctly
-  writable.cork();
-  writable.write('third chunk');
-  writable.end();
-
-  // End causes an uncork() as well
-  assert.strictEqual(writable._writableState.corked, 0);
-  assert.strictEqual(writable._writableState.bufferedRequestCount, 0);
-}