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

diff --git a/cli/tests/node_compat/test/parallel/test-child-process-execsync-maxbuf.js b/cli/tests/node_compat/test/parallel/test-child-process-execsync-maxbuf.js
deleted file mode 100644
index 703896ef1..000000000
--- a/cli/tests/node_compat/test/parallel/test-child-process-execsync-maxbuf.js
+++ /dev/null
@@ -1,76 +0,0 @@
-// deno-fmt-ignore-file
-// deno-lint-ignore-file
-
-// Copyright Joyent and Node contributors. All rights reserved. MIT license.
-// Taken from Node 18.8.0
-// This file is automatically generated by "node/_tools/setup.ts". Do not modify this file manually
-
-// TODO(cjihrig): This should use Node's -e instead of Deno's eval CLI arg.
-
-'use strict';
-require('../common');
-
-// This test checks that the maxBuffer option for child_process.spawnSync()
-// works as expected.
-
-const assert = require('assert');
-const { getSystemErrorName } = require('util');
-const { execSync } = require('child_process');
-const msgOut = 'this is stdout';
-const msgOutBuf = Buffer.from(`${msgOut}\n`);
-
-const args = [
-  'eval',
-  `"console.log('${msgOut}')";`,
-];
-
-// Verify that an error is returned if maxBuffer is surpassed.
-{
-  assert.throws(() => {
-    execSync(`"${process.execPath}" ${args.join(' ')}`, { maxBuffer: 1 });
-  }, (e) => {
-    assert.ok(e, 'maxBuffer should error');
-    assert.strictEqual(e.code, 'ENOBUFS');
-    assert.strictEqual(getSystemErrorName(e.errno), 'ENOBUFS');
-    // We can have buffers larger than maxBuffer because underneath we alloc 64k
-    // that matches our read sizes.
-    assert.deepStrictEqual(e.stdout, msgOutBuf);
-    return true;
-  });
-}
-
-// Verify that a maxBuffer size of Infinity works.
-{
-  const ret = execSync(
-    `"${process.execPath}" ${args.join(' ')}`,
-    { maxBuffer: Infinity }
-  );
-
-  assert.deepStrictEqual(ret, msgOutBuf);
-}
-
-// Default maxBuffer size is 1024 * 1024.
-{
-  assert.throws(() => {
-    execSync(
-      `"${process.execPath}" eval "console.log('a'.repeat(1024 * 1024))"`
-    );
-  }, (e) => {
-    assert.ok(e, 'maxBuffer should error');
-    assert.strictEqual(e.code, 'ENOBUFS');
-    assert.strictEqual(getSystemErrorName(e.errno), 'ENOBUFS');
-    return true;
-  });
-}
-
-// Default maxBuffer size is 1024 * 1024.
-{
-  const ret = execSync(
-    `"${process.execPath}" eval "console.log('a'.repeat(1024 * 1024 - 1))"`
-  );
-
-  assert.deepStrictEqual(
-    ret.toString().trim(),
-    'a'.repeat(1024 * 1024 - 1)
-  );
-}