Migrate to vitest

[exoego]

Closes #1591

Note

After this PR, @jest/schemas dependency remains in package-lock.json.
This is because Vitest's snapshot mechanism (Jest has it too) depends on pretty-format that depends on @jest/schemas.

Performance comparison

The below numbers are collected in get-global-config directory.

Before

❯ npm run test

> test
> jest

 PASS  src/run.test.ts
  ✓ default (2 ms)
  ✓ plan_workflow_name is required (13 ms)
  ✓ customize (1 ms)

Test Suites: 1 passed, 1 total
Tests:       3 passed, 3 total
Snapshots:   0 total
Time:        2.024 s
Ran all test suites.

After

❯ npm run test

> test
> vitest --run


 RUN  v1.4.0 /Users/exoego/IdeaProjects/tfaction/get-global-config

 ✓ src/run.test.ts (3)
   ✓ default
   ✓ plan_workflow_name is required
   ✓ customize

 Test Files  1 passed (1)
      Tests  3 passed (3)
   Start at  21:27:30
   Duration  232ms (transform 31ms, setup 0ms, collect 18ms, tests 3ms, environment 0ms, prepare 65ms)

[suzuki-shunsuke]

Thank you for your contribution!

This is still draft, but I leave a comment.

As I mentioned at #1528 (review) ,
could you open an issue (in this case, I prefer an issue over a discussion because the task is clear) before sending a pull request?
And in the issue, please describe why we migrate to Vitest.
Of course I know the background of this pull request, #1528 (comment)
but the issue would be useful when someone will track the change.
I don't want to accept a pull request without any issue or discussion except for trivial fix (typo, etc).

[suzuki-shunsuke]

Thank you for your contribution!

This is still draft, but I leave a comment.

As I mentioned at #1528 (review) , could you open an issue (in this case, I prefer an issue over a discussion because the task is clear) before sending a pull request? And in the issue, please describe why we migrate to Vitest. Of course I know the background of this pull request, #1528 (comment) but the issue would be useful when someone will track the change. I don't want to accept a pull request without any issue or discussion except for trivial fix (typo, etc).

Thank you for opening the issue.

• Consider migration from Jest to Vitest #1591