chore: Disable ESLint warnings for removed rules

[Gudahtt]

Explanation

These two rules were removed from our shared config. We can remove them completely rather than suppressing these warnings.

References

This is a follow-up to #7103

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Removes warning thresholds and rule entries for jest/no-conditional-in-test and @typescript-eslint/no-unsafe-enum-comparison across config and thresholds.

• ESLint config:
  • Remove jest/no-conditional-in-test from test rules in eslint.config.mjs.
  • Remove @typescript-eslint/no-unsafe-enum-comparison from TypeScript rules in eslint.config.mjs.
• Warning thresholds:
  • Purge occurrences of jest/no-conditional-in-test and @typescript-eslint/no-unsafe-enum-comparison across eslint-warning-thresholds.json.
  • Minor cleanup of related per-file entries (retaining other warnings).

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

[cryptodev-2s]

LGTM!