chore(deps-dev): update eslint to v10

[mturac]

Fixes #955

Summary

• update ESLint and @eslint/js to v10
• replace the import lint plugin with an ESLint 10-compatible implementation while preserving the existing import and Node protocol checks
• update the local license rule for ESLint 10's rule-context properties
• align the supported Node.js versions with ESLint 10's engine requirements
• preserve the current recommended-rule baseline during the major upgrade

Testing

• npm ci
• npm run check-format
• npm run typecheck
• npm run test

[Lightning00Blade]

Let's not change the deps for now, we can simply add the following code to the package.json:

  "overrides": {
    "eslint-plugin-import": {
      "eslint": "$eslint"
    }
  },

Which will force use EsLint v10 which is only incompatible because of eslint-plugin-import does not declare it an acceptable peer dependency, but code wise it works.

[Lightning00Blade]

Revert this change. The field say what our package supports, local development can require a different ones.

[Lightning00Blade]

This showed up again.

[mturac]

Restored the top-level package engine range and lockfile mirror to ^20.19.0 || ^22.12.0 || >=23, while keeping the eslint-plugin-import override.

Validation:

• npm run check-format
• npm run build
• npm run test -- --test-concurrency=1

[mturac]

Updated this to keep the existing eslint-plugin-import setup, add the ESLint peer override, and restore the package engine range.

Validation:

• npm run check-format
• npm run build
• npm run test -- --test-concurrency=1

[OrKoN]

Thanks for the PR! @Lightning00Blade could you please re-gen package-lock locally for this fix?

[mturac]

Rebased on latest main and regenerated the lockfile locally with npm install --package-lock-only; it produced no tracked changes.

Validation:

• npm run check-format
• npm run build
• npm run test -- --test-concurrency=1