refactor: migrate jest to vitest

[tatomyr]

What/Why/How?

Migrated from Jest to Vitest.

Here's a short guidance:

jest-to-vitest migration guide

jest.fn

1. Replace jest.fn() with vi.fn()

jest.SpyInstance

1. The file needs to include import { MockInstance } from 'vitest';
2. Replace let spy: jest.SpyInstance; with let spy: MockInstance;

vi.spyOn

1. When spying on path, needed to use this hack (doesn't work without shallow copying):

vi.mock('node:path', async () => {
  const actual = await vi.importActual('node:path');
  return { ...actual };
});

vi.mocked

1. Replace this:

existsSync as jest.Mock<any, any>

with this:

vi.mocked(existsSync)

This passes the actual types down to the mocked function and helps maintain consistency.

---

Reference

Testing

• Smokes are failing due to an external issue (fixed in feat(respect): introduce global execution timeout-timer #2003)
• E2E are unstable due to another external issue (also fixed in feat(respect): introduce global execution timeout-timer #2003)
• Vale test is failing due to enormous diff (passes locally)

Screenshots (optional)

Check yourself

• Code changed? - Tested with redoc/reference-docs/workflows (internal)
• All new/updated code is covered with tests
• New package installed? - Tested in different environments (browser/node)

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: 553a76e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage report

Multiple errors occurred

 1 | Error: The process '/opt/hostedtoolcache/node/20.18.3/x64/bin/npm' failed with exit code 1
 2 | Coverage output file not found. (file "report.json" not found)
 3 | Getting code coverage data failed.

St.❔	Category	Percentage	Covered / Total
🟢	Statements	81.16%	6751/8318
🟡	Branches	69.63%	2784/3998
🟡	Functions	76.68%	1105/1441
🟢	Lines	81.57%	6434/7888

Test suite run success

1278 tests passing in 189 suites.

Report generated by 🧪jest coverage report action from 5a185d8