Test ESLint configs

[Mrtenz]

Closes #229.

By running ESLint on a dummy file, we can verify that our rules are valid. This can catch errors like typos in rules, non-existent rules, etc.

I'm using Jest for testing here. This could also let us implement rule validation on a per-package basis in the future.

[socket-security]

Socket Security Pull Request Report

👍 No new dependency issues detected in pull request

Pull request report summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script confusion	✅ 0 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@2.4.2

Ignoring: jest@29.3.1, jest-cli@29.3.1

Powered by socket.dev

[Mrtenz]

@SocketSecurity ignore jest@29.3.1
@SocketSecurity ignore jest-cli@29.3.1

[Gudahtt]

LGTM!

[mcmire]

@Mrtenz Just noticed this. Great idea!