test: run accounts-controller on Vitest

[cryptodev-2s]

Explanation

Moves @metamask/accounts-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).

createExpectedInternalAccount moves out of tests/mocks.ts into tests/expectations.ts. It uses expect.any(Number), and an asymmetric matcher from one runner means nothing to the other, while mocks.ts is imported by assets-controllers, still on Jest.

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 migration with no production API changes; the split of Vitest-specific matchers into expectations.ts preserves Jest compatibility for shared mocks.

Overview
Migrates @metamask/accounts-controller from Jest to Vitest as part of the repo-wide test-runner rollout. Production code is unchanged; only test tooling and test files are touched.

The package drops jest.config.cjs and Jest-related devDependencies in favor of vitest.config.mjs (same coverage thresholds as before) and vitest scripts in package.json. test-runner-package-map.cjs no longer lists this package as Jest-based. Package tsconfig.json sets compilerOptions.types to [] so repo-wide Jest types do not apply while Vitest runs without globals.

Tests import describe/expect/vi explicitly and replace jest.* with vi.* (including vi.importActual for the uuid mock). createExpectedInternalAccount moves from tests/mocks.ts into new tests/expectations.ts because it uses Vitest’s expect.any(Number); mocks.ts stays free of Vitest so Jest consumers (e.g. assets-controllers) can keep importing it.

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