fix: never instrument eslint configs for coverage

[nlf]

this is an alternative fix to the issue we saw where we'd blow up the call stack when the test runner tried to instrument the eslint config. adding our own internal eslint config to the coverage exclusions did so in too specific of a way, so instead i tweaked the require extension such that it will never instrument an eslint config of any type.

this is necessary to make it so users don't have to explicitly ignore their own .eslintrc.js if they have one