Fix eslint config

[peterwilsoncc]

Describe the bug

Running eslint on this repo fails with the message that the WordPress eslint config is not installed.

While working on #351 I wasn't able to get it working so it will need a little further investigation as to the cause.

Steps to Reproduce

1. Run npm ci
2. Run npx wp-scripts lint-js
3. Observe failure.

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[mariozenmedina]

I dug into this and found that the initial failure is caused by ESLint plugin resolution.

The root .eslintrc extends plugin:@wordpress/eslint-plugin/recommended, but @wordpress/eslint-plugin is only available as a nested dependency of @wordpress/scripts, so ESLint cannot resolve it from the project root.

There is a similar issue in tests/cypress/.eslintrc, which extends plugin:cypress/recommended without declaring eslint-plugin-cypress.

After making those plugins resolvable, ESLint reaches another dependency-resolution issue with eslint-import-resolver-typescript: the newer resolver interface is not compatible with this repo's current ESLint 8 / eslint-plugin-import setup, causing Resolve error: typescript with invalid interface loaded as resolver.

I have a PR prepared that adds the missing direct ESLint dependencies and pins the TypeScript import resolver to a compatible version. After that, wp-scripts lint-js loads the configs/plugins successfully and reaches the existing lint violations, mostly CRLF/Prettier-related, which seem separate from this setup issue.