chore(deps-dev): bump eslint-dependencies group (ESLint v9→v10 + related packages)

[Copilot]

Dependabot bump of 6 ESLint-ecosystem packages, including a major version jump for ESLint itself (9.x → 10.0.0/10.0.1).

Description

• eslint: 9.39.2 → 10.0.0
• @eslint/js: 9.39.2 → 10.0.1
• @stylistic/eslint-plugin: 5.7.1 → 5.8.0
• @typescript-eslint/eslint-plugin: 8.54.0 → 8.55.0
• @typescript-eslint/parser: 8.54.0 → 8.55.0
• globals: 17.1.0 → 17.3.0

⚠️ Blocked: eslint-plugin-import@2.32.0 declares peer support only for eslint@^2–^9. Bumping ESLint to v10 causes an npm peer dependency conflict and breaks npm install.

Options: hold ESLint at v9 until eslint-plugin-import adds ESLint v10 support, or replace it with a v10-compatible fork such as eslint-plugin-import-x.

Related Issue

ESLint v10 peer dependency conflict with eslint-plugin-import.

Motivation and Context

Routine dependency maintenance. ESLint v10 is a major release; the rest of the bumps are non-breaking minor/patch updates.

How Has This Been Tested?

CI fails at npm install due to the peer dep conflict described above — no tests can run until this is resolved.

Types of changes

• Chore (non-breaking change which refactors / improves the existing code base)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• 🔴 My change requires a change to the documentation.
• 🔴 I have updated the documentation accordingly.
• 🔴 I have read the CONTRIBUTING document.
• 🔴 I have added tests to cover my changes.
• 🔴 All new and existing tests passed.

---

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