chore: update @eslint/* dep, add legacy-peer-deps, use ESLint v10

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

This PR was motivated by eslint/json#187 (comment).

Currently, when updating @eslint/core to v1.0.0, CI fails because @eslint/core@1.0.0 does not match ESLint v9

@eslint/core@1.0.0 includes type information for ESLint v10, which causes the type mismatch.

So, I've updated ESLint to >=10.0.0-alpha.0 <10.0.0 || ^10.0.1. (Ref: https://github.com/eslint/eslint/blob/main/packages/eslint-config-eslint/package.json#L66)

---

When I update ESLint to >=10.0.0-alpha.0 <10.0.0 || ^10.0.1, the following error occurs, so I added the legacy-peer-deps option to .npmrc.

This change follows the approach in eslint/eslint#20281

What changes did you make? (Give an overview)

In this PR, I've updated @eslint/core, add legacy-peer-deps, and use ESLint v10 pre-release.

Related Issues

Ref: #584, #586, eslint/json#187 (comment), eslint/eslint#20281

Is there anything you'd like reviewers to focus on?

N/A

---

TODO for myself:

scopeManager.addGlobals:

• https://eslint.org/docs/next/use/migrate-to-10.0.0#-new-requirements-for-scopemanager-implementations
• Question: how come function references on the global scope are not closed js#665
• feat!: Resolve references to global var/function, add addGlobals() js#682

[lumirlumir]

Unlike the PRs in JSON and CSS, the Markdown plugin needs further investigation to support ESLint v10. I'm marking this as a draft for now and will investigate it soon.

[mdjermanovic]

Same question as eslint/json#190 (comment). We can clarify there, just wanted to leave a note here as well so that we don't merge until this is clarified.

[mdjermanovic]

We should also decide on whether we want this plugin to still support ESLint v9 when ESLint v10 final is released.