Add ESLint8 to peerDependencies

[IvanGoncharov]

No description provided.

[IvanGoncharov]

@coreyfarrell This change blocks us from upgrading to ESLint v8.
CI fails since package-lock.json is not updated.
I can update it locally but I have a new NPM version that will rewrite the entire file.
Can you please take a look?
Also would be great if you update package-lock.json to v2.

[IvanGoncharov]

@coreyfarrell Can you please look into it?

[dhurlburtusa]

Did you consider using >=6.0.0 for the version instead of ^6.0.0 || ^7.0.0 || ^8.0.0? The former will include v9, v10, etc of ESLint. The latter won't.
The pro is that we won't have to keep updating the peer dependency versions every time a new compatible ESLint version comes out. The con is that there is a possibility a new ESLint version is incompatible. (My guess is that that would be very unlikely. And if it does happen, then the behavior of the developer will still be the same (don't use with the incompatible ESLint) but they won't get an error message when running npm install or similar until the incompatible version is filtered out.)