chore: migrate to ESLint v9 flat config and update linting tools

[Copilot]

Migrates ESLint configuration from legacy .eslintrc.cjs format to v9 flat config format and updates all linting dependencies to latest versions.

Changes

ESLint Migration

• Migrated from .eslintrc.cjs to eslint.config.mjs flat config format
• Removed deprecated .eslintignore (ignores now inline in config)
• Removed --ext flag from lint scripts (auto-detected in v9)
• Added @eslint/compat + @eslint/eslintrc for legacy config compatibility
• Used fixupConfigRules() to bridge airbnb-typescript/v8 incompatibility

Package Updates

• ESLint: v8.57.1 → v9.39.1
• @typescript-eslint/*: v7.18.0 → v8.47.0
• eslint-config-prettier: v9.1.0 → v10.1.8
• eslint-plugin-react-hooks: v4.6.2 → v7.0.1
• eslint-plugin-jsdoc: v50.6.3 → v61.2.1
• eslint-plugin-storybook: v0.9.0 → v10.0.8
• prettier: v3.5.2 → v3.6.2
• Plus other minor plugin updates

Configuration Example

Before (.eslintrc.cjs):

module.exports = {
  root: true,
  parser: '@typescript-eslint/parser',
  extends: ['airbnb-typescript', 'prettier'],
  // ...
}

After (eslint.config.mjs):

import { fixupConfigRules } from '@eslint/compat';
import { FlatCompat } from '@eslint/eslintrc';
import js from '@eslint/js';

export default [
  { ignores: ['dist/**', 'build/**'] },
  js.configs.recommended,
  ...fixupConfigRules(
    compat.extends('airbnb-typescript', 'prettier')
  ),
  // ...
]

All existing rules and code style preserved. Build, type-check, and linting verified.

Original prompt

Update Eslint and prettier, migrating the config format to the new version.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

---

This change is 

[changeset-bot]

⚠️ No Changeset found

Latest commit: ec63b5e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Your pull request title did not conform to conventional commits standards. Our upcoming automated release pipeline will automatically determine
the proper release version based on your pull request title.
Cheat Sheet

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit