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

diff --git a/cli/tests/node_compat/test/parallel/test-path-zero-length-strings.js b/cli/tests/node_compat/test/parallel/test-path-zero-length-strings.js
deleted file mode 100644
index 5fa1eafbf..000000000
--- a/cli/tests/node_compat/test/parallel/test-path-zero-length-strings.js
+++ /dev/null
@@ -1,46 +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';
-
-// These testcases are specific to one uncommon behavior in path module. Few
-// of the functions in path module, treat '' strings as current working
-// directory. This test makes sure that the behavior is intact between commits.
-// See: https://github.com/nodejs/node/pull/2106
-
-require('../common');
-const assert = require('assert');
-const path = require('path');
-const pwd = process.cwd();
-
-// Join will internally ignore all the zero-length strings and it will return
-// '.' if the joined string is a zero-length string.
-assert.strictEqual(path.posix.join(''), '.');
-assert.strictEqual(path.posix.join('', ''), '.');
-assert.strictEqual(path.win32.join(''), '.');
-assert.strictEqual(path.win32.join('', ''), '.');
-assert.strictEqual(path.join(pwd), pwd);
-assert.strictEqual(path.join(pwd, ''), pwd);
-
-// Normalize will return '.' if the input is a zero-length string
-assert.strictEqual(path.posix.normalize(''), '.');
-assert.strictEqual(path.win32.normalize(''), '.');
-assert.strictEqual(path.normalize(pwd), pwd);
-
-// Since '' is not a valid path in any of the common environments, return false
-assert.strictEqual(path.posix.isAbsolute(''), false);
-assert.strictEqual(path.win32.isAbsolute(''), false);
-
-// Resolve, internally ignores all the zero-length strings and returns the
-// current working directory
-assert.strictEqual(path.resolve(''), pwd);
-assert.strictEqual(path.resolve('', ''), pwd);
-
-// Relative, internally calls resolve. So, '' is actually the current directory
-assert.strictEqual(path.relative('', pwd), '');
-assert.strictEqual(path.relative(pwd, ''), '');
-assert.strictEqual(path.relative(pwd, pwd), '');