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

diff --git a/tests/testdata/publish/invalid_fast_check.out b/tests/testdata/publish/invalid_fast_check.out
new file mode 100644
index 000000000..d18be45fe
--- /dev/null
+++ b/tests/testdata/publish/invalid_fast_check.out
@@ -0,0 +1,16 @@
+Checking fast check type graph for errors...
+error[zap-missing-explicit-return-type]: missing explicit return type in the public API
+ --> [WILDCARD]mod.ts:2:17
+  | 
+2 | export function getRandom() {
+  |                 ^^^^^^^^^ this function is missing an explicit return type
+  = hint: add an explicit return type to the function
+
+  info: all functions in the public API must have an explicit return type
+  docs: https://jsr.io/go/zap-missing-explicit-return-type
+
+This package contains Zap errors. Although conforming to Zap will
+significantly improve the type checking performance of your library,
+you can choose to skip it by providing the --no-zap flag.
+
+error: Found 1 problem