test: run network-controller on Vitest

[cryptodev-2s]

Explanation

Moves @metamask/network-controller to Vitest.

References

• Part of the Jest to Vitest migration, see test: add Vitest alongside Jest #10546 for 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 migration only; production network-controller runtime code is unchanged aside from lint-suppression bookkeeping.

Overview
Migrates @metamask/network-controller from Jest (+ TSTyche) to Vitest as part of the broader test-runner migration.

The package drops jest.config.cjs and Jest-related devDependencies; package.json scripts now call vitest, with a merged vitest.config.js that adds tests/**/*.test.ts (large NetworkController suites outside src/), enables typecheck for *.test-d.ts (TSTyche → expectTypeOf().toExtend()), and sets Vitest coverage thresholds.

Test code is mechanically updated (jest → vi, fake timers, mocks). Notable fixes beyond rename: waitForPromiseToBeFulfilledAfterRunningAllTimers yields a real macrotask before vi.runAllTimersAsync so nock replies settle; onBreak expectations use HttpError(503) instead of generic Error; ignoreRejection lives in tests/vitest/helpers.ts; Jest-only jest-when removed; jsdom test environment removed (node passes). The package is removed from the Jest test-runner-package-map.

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