test: run keyring-controller on Vitest

[cryptodev-2s]

Explanation

Moves @metamask/keyring-controller to Vitest. One of a stack on top of #10546, which added Vitest without migrating anything.

Add vitest.config.mts, delete jest.config.cjs, swap the test scripts and dev dependencies, point the package tsconfig off the repo wide types: ["jest"], and rewrite the test files (jest.* to vi.*, jest.Mocked to the imported Vitest type, requireActual to an awaited importActual, and an explicit vitest import per file since globals is off).

knip.config.mts gains a uuid ignore: here it is only ever a module name string, in vi.mock and vi.importActual, which knip does not trace. Coverage thresholds restated at measured values. Istanbul on esbuild output counts statements slightly differently from babel on ts-jest output, within about a point.

Tests pass with coverage thresholds enforced. yarn lint and yarn constraints are green on this branch alone.

References

• Stacked on test: add Vitest alongside Jest #10546, which explains the shared setup

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
  • Not applicable, test only change. Carries the no-changelog label.
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
  • None.

---

Note

Low Risk
Test-only and build-tooling changes; no production KeyringController runtime behavior is modified.

Overview
@metamask/keyring-controller moves off Jest onto Vitest: jest.config.cjs is removed, vitest.config.mjs is added (with coverage thresholds retuned for Istanbul/esbuild), and package.json test scripts and devDependencies swap Jest for Vitest.

Test code is updated mechanically—jest.* → vi.*, explicit vitest imports (globals off), vi.importActual for the uuid mock, and tsconfig.json sets types: [] so repo-wide Jest types do not apply. Smaller test files and mockErc4337Keyring get the same treatment.

Tooling follows the package: @metamask/keyring-controller is dropped from the Jest workspace list in test-runner-package-map.cjs, knip ignores uuid as a mock module string, and oxlint-suppressions.json drops the deleted Jest config entry and adjusts test-file counts.

^{Reviewed by Cursor Bugbot for commit dba4dd3. Bugbot is set up for automated code reviews on this repo. Configure here.}