replace jasmine with vitest

[dynst]

Vitest has decent defaults so a configuration file may not even be required.

Blocked on:
#1809 & #1832 & #1833 #1004

Converting is easy now that xit is in use:

- `xit` = `it.skip` - `jasmine.stringMatching` = [`expect.stringMatching`](https://vitest.dev/api/expect.html#expect-stringmatching) - `expect(a).withContext(b)` = `expect(a, b)` - [`expectAsync(p).toBeRejectedWithError(/regex/)`](https://jasmine.github.io/api/4.6/async-matchers.html) = `expect(p).rejects.toThrowError(/regex/)`

And --quiet is passed by the coverage script, so that has to be removed when replacing the Jasmine CJS file.

cosmjs/packages/utils/jasmine-testrunner.cjs

Line 29 in ca243f5

displaySuccessful: !process.argv.includes("--quiet"),

cosmjs/packages/utils/package.json

Line 35 in ca243f5

"coverage": "nyc --reporter=text --reporter=lcov yarn test --quiet",

The default timeout in Vitest is 5s but some tests need longer than that. The slow server tests have a 5s server-side delay, so:

[@cosmjs/socket]:  ✓ src/streamingsocket.spec.ts (6 tests) 9446ms
[@cosmjs/socket]:    ✓ StreamingSocket > can connect to slow server  7408ms

socket tests that spawn child processes with exec() are heavily entangled with the others. If one test times out, it causes completely unrelated tests to fail. And they can't be run in parallel (Vitest has per-spec-file parallelism by default).

cosmjs/packages/socket/src/reconnectingsocket.spec.ts

Lines 206 to 209 in ca243f5

	}, 2000);
	}, 2000);
	});
	}, 1000);

[dynst]

Why is there a --stream argument that's always passed to all the tests? And why is it in the workflow config, instead of in the root-level package.json, or individual packages' scripts?

cosmjs/.github/workflows/test.yml

Line 103 in 8fb7421

run: yarn test --stream

cosmjs/.circleci/config.yml

Line 154 in 31db121

yarn test --stream

Is there another way to do whatever it is it's doing?

0d41983

Edit: #1850