Remove ESLint rules now covered by Biome

[IvanKiral]

Motivation

Remove ESLint rules that are now covered by Biome linter to avoid duplicate linting and reduce configuration overhead.

Rules Removed

TypeScript rules (from index.js)

• @typescript-eslint/no-unnecessary-condition → no-unnecessary-conditions
• @typescript-eslint/switch-exhaustiveness-check → use-exhaustive-switch-cases
• @typescript-eslint/await-thenable → use-await-thenable - !! was not working very well decided to revert this!
• @typescript-eslint/no-floating-promises → no-floating-promises
• @typescript-eslint/no-for-in-array → no-for-in
• @typescript-eslint/no-misused-promises → no-misused-promises
• @typescript-eslint/no-non-null-asserted-optional-chain → no-non-null-asserted-optional-chain
• @typescript-eslint/unified-signatures → use-unified-type-signatures
• @typescript-eslint/require-array-sort-compare → use-array-sort-compare

React rules (from react.js)

• react/jsx-boolean-value → no-implicit-boolean
• react/self-closing-comp → use-self-closing-elements
• react/jsx-no-leaked-render → no-leaked-render
• react/prefer-stateless-function → use-react-function-components

Biome rules still pending (PRs not merged yet)

The following rules are tracked for future removal once their Biome equivalents are released:

• @typescript-eslint/prefer-string-starts-ends-with - PR #8582
• @typescript-eslint/prefer-nullish-coalescing - Issue #8043
• react/jsx-no-bind - PR #7410

Checklist

• Code follows coding conventions held in this repo
• Automated tests have been added
• Tests are passing
• Docs have been updated (if applicable)
• Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test

No manual testing required. This change removes rules from ESLint configuration. Verify by running ESLint to ensure no configuration errors.