test: run base-controller on Vitest

[cryptodev-2s]

Explanation

Moves @metamask/base-controller to Vitest.

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 only; no changes to published runtime code or package APIs.

Overview
Migrates @metamask/base-controller from Jest to Vitest, following the shared monorepo Vitest setup (stacked on the parent PR).

The package drops jest.config.cjs and Jest-related devDependencies, adds vitest.config.mjs (including 100% coverage thresholds carried over from Jest), and updates package.json test scripts to vitest run / vitest watch. BaseController.test.ts switches to explicit Vitest imports (describe, expect, it, vi) and replaces jest.fn / jest.spyOn with vi.

tsconfig.json sets "types": [] so repo-wide Jest types do not apply under Vitest. @metamask/base-controller is removed from the Jest test-runner-package-map.cjs list and from the related oxlint-suppressions.json entry for the deleted Jest config.

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