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, 40 insertions, 0 deletions

diff --git a/tests/unit_node/_test_utils.ts b/tests/unit_node/_test_utils.ts
new file mode 100644
index 000000000..3942cf0a9
--- /dev/null
+++ b/tests/unit_node/_test_utils.ts
@@ -0,0 +1,40 @@
+// Copyright 2018-2024 the Deno authors. All rights reserved. MIT license.
+
+import { assert, assertStringIncludes } from "@test_util/std/assert/mod.ts";
+
+/** Asserts that an error thrown in a callback will not be wrongly caught. */
+export async function assertCallbackErrorUncaught(
+  { prelude, invocation, cleanup }: {
+    /** Any code which needs to run before the actual invocation (notably, any import statements). */
+    prelude?: string;
+    /**
+     * The start of the invocation of the function, e.g. `open("foo.txt", `.
+     * The callback will be added after it.
+     */
+    invocation: string;
+    /** Called after the subprocess is finished but before running the assertions, e.g. to clean up created files. */
+    cleanup?: () => Promise<void> | void;
+  },
+) {
+  // Since the error has to be uncaught, and that will kill the Deno process,
+  // the only way to test this is to spawn a subprocess.
+  const p = new Deno.Command(Deno.execPath(), {
+    args: [
+      "eval",
+      "--unstable",
+      `${prelude ?? ""}
+  
+        ${invocation}(err) => {
+          // If the bug is present and the callback is called again with an error,
+          // don't throw another error, so if the subprocess fails we know it had the correct behaviour.
+          if (!err) throw new Error("success");
+        });`,
+    ],
+    stderr: "piped",
+  });
+  const { stderr, success } = await p.output();
+  const error = new TextDecoder().decode(stderr);
+  await cleanup?.();
+  assert(!success);
+  assertStringIncludes(error, "Error: success");
+}