Resolve build job failure by aligning ESLint package versions

[Copilot]

The build GitHub Actions job failed at dependency installation due to an npm peer-resolution conflict between eslint@9 and @eslint/js@10. This change restores install-time compatibility by keeping @eslint/js on the ESLint 9 line.

• Root cause

  • @eslint/js@10.x declares a peer requirement for eslint@^10, while the repo uses eslint@^9.39.2.
  • npm install exits with ERESOLVE in CI before any build steps execute.

• Change made

  • Updated devDependencies to pin @eslint/js to a compatible 9.x range.
  • Regenerated lockfile entries so the resolved @eslint/js package matches the new version constraint and no longer introduces the ESLint 10 peer requirement.

• Scope

  • Dependency metadata only (package.json, package-lock.json).
  • No application/runtime code paths were modified.

// package.json
{
  "devDependencies": {
    "@eslint/js": "^9.39.5",
    "eslint": "^9.39.2"
  }
}