test: run user-operation-controller on Vitest

[cryptodev-2s]

Explanation

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

Four mocked constructors needed mockImplementation(function () { ... }): Vitest refuses mockReturnValue on a mock called with new. Those four sites caused 84 failures, so the diff reads worse than it is. 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 and tooling changes only; production source under src/ is not modified in this diff.

Overview
Migrates @metamask/user-operation-controller from Jest to Vitest, aligning it with the repo’s shared Vitest package setup.

Removes jest.config.cjs and Jest-related devDependencies/scripts; adds vitest.config.mjs (merged from vitest.config.packages.mjs) with coverage thresholds retuned for Vitest/Istanbul. Package tsconfig.json clears types so Jest globals are not pulled in. Test files now import Vitest explicitly and use vi.* instead of jest.*, including async importActual for partial mocks and mockImplementation on constructor mocks where Vitest disallows mockReturnValue with new.

@metamask/user-operation-controller is dropped from test-runners.cjs’s Jest package list; oxlint-suppressions.json is trimmed for removed Jest-only lint entries.

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