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/npm/registry/@denotest/child-process-fork/1.0.0/index.js b/cli/tests/testdata/npm/registry/@denotest/child-process-fork/1.0.0/index.js
deleted file mode 100644
index 0482be404..000000000
--- a/cli/tests/testdata/npm/registry/@denotest/child-process-fork/1.0.0/index.js
+++ /dev/null
@@ -1,20 +0,0 @@
-const path = require("path");
-
-function childProcessFork(path) {
-  const command = new Deno.Command(Deno.execPath(), {
-    args: ["run", "-A", path],
-    env: {
-      "DENO_DONT_USE_INTERNAL_NODE_COMPAT_STATE": Deno[Deno.internal].core.ops.op_npm_process_state(),
-    }
-  });
-  const child = command.spawn();
-  child.status.then(() => {
-    console.log("Done.");
-  });
-}
-
-module.exports = {
-  run() {
-    childProcessFork(path.join(__dirname, "forked_path.js"));
-  }
-};