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

diff --git a/cli/tests/testdata/run/015_duplicate_parallel_import.js b/cli/tests/testdata/run/015_duplicate_parallel_import.js
deleted file mode 100644
index 2fbe2c732..000000000
--- a/cli/tests/testdata/run/015_duplicate_parallel_import.js
+++ /dev/null
@@ -1,20 +0,0 @@
-// Importing the same module in parallel, the module should only be
-// instantiated once.
-
-const promises = new Array(100)
-  .fill(null)
-  .map(() => import("../subdir/mod1.ts"));
-
-Promise.all(promises).then((imports) => {
-  const mod = imports.reduce((first, cur) => {
-    if (typeof first !== "object") {
-      throw new Error("Expected an object.");
-    }
-    if (first !== cur) {
-      throw new Error("More than one instance of the same module.");
-    }
-    return first;
-  });
-
-  mod.printHello3();
-});