Release/14.1.0

[Gudahtt]

This release includes a few minor improvements across a few different packages.

---

Note

Publishes v14.1.0 across packages with TypeScript 5.6–5.8 support and several Jest/base ESLint rule adjustments.

• Release: bump versions to 14.1.0 in root, @metamask/eslint-config, @metamask/eslint-config-jest, and @metamask/eslint-config-typescript.
• Base (@metamask/eslint-config):
  • Loosen promise/catch-or-return and promise/param-names.
• Jest (@metamask/eslint-config-jest):
  • Replace @typescript-eslint/unbound-method with jest/unbound-method.
  • Remove jest/no-conditional-in-test.
• TypeScript (@metamask/eslint-config-typescript):
  • Add support for TypeScript 5.6.x–5.8.x.
  • Disable @typescript-eslint/no-unsafe-enum-comparison.
  • Loosen:
    • @typescript-eslint/prefer-promise-reject-errors (allow unknown).
    • @typescript-eslint/naming-convention (import names).
    • @typescript-eslint/switch-exhaustiveness-check (allow default).

^{Written by Cursor Bugbot for commit db61ab4. This will update automatically on new commits. Configure here.}

[Gudahtt]

The only blocker here is manual testing. I wanted to test this in core first, but I ran into some obstacles the last time I tried.

[Gudahtt]

I tested this in core.

I did find some new errors from jest/unbound-method. That rule was enabled in #391. We had considered it non-breaking because it was strictly looser than @typescript-eslint/unbound-method, but @typescript-eslint/unbound-method was disabled in core.

I think it's still fair to consider this non-breaking, since it's looser than the previous ruleset. But in practice it might end up being breaking because of disabled rules.

[Gudahtt]

I've updated the changelog to clarify that change, and explain why it's usually non-breaking but not always.