Add ESLint v10 support to hermes-eslint

[JasonWeinzierl]

Summary

Add support to hermes-eslint for ESLint v10.

1. Added support for ScopeManager.addGlobals().
   • Since this scope manager is heavily based on typescript-eslint's scope manager, I followed their changes in feat(scope-manager): support ScopeManager#addGlobals typescript-eslint/typescript-eslint#11914 to ensure it was correct.
   • Also followed their unit test changes.
2. Added eslint to hermes-eslint's peer dependencies as optional, for documenting supported versions.
   • Everything works as far back as ESLint v4. I created a demo repository that tests compatibility: https://github.com/JasonWeinzierl/hermes-eslint-compatibility-test
   • Also moved esrecurse to devDependencies since it's not required by the published code.
3. Migrated the internal eslint config to the flat config instead of eslintrc.
   • Several incompatible plugins were swapped out for their updated forks (ft-flow and eslint-comments).
   • Upgraded the internal eslint version to v9. Cannot go to v10 because some plugins use APIs not available in v10 (e.g. context.getSourceCode()). For example, feat!: ESLint v10 and flat config support flow-typed/eslint-plugin-ft-flow#71 recursively needs hermes-eslint to be upgraded first.
   • Installed @eslint/js as a defensive measure: eslint v10 will require this to be installed.
4. Updated README of hermes-eslint with flat config example.

Note: it would be nice to see #1651 merged, since these packages published on npm do not display links to this repository, so it took me a minute to find this.

Test Plan

Ran the following commands:

# (first I set up the repository and built the wasm, then I did the following)
cd tools/hermes-parser/js
yarn install
yarn build ../../../build-wasm/bin/hermes-parser-wasm.js ../../../include
yarn test
yarn lint
yarn format

Build, test, and lint passes.

Demonstration of peer dependency compatibility: https://github.com/JasonWeinzierl/hermes-eslint-compatibility-test

[gkz]

Hi @JasonWeinzierl, thanks for your work! We will take a look at this, though we will need to confirm that nothing breaks internally.

[JasonWeinzierl]

Rebased onto static_h