feat: add eslintQuiet option (#340)

[jeffshaver]

This PR adds a quiet option so that warnings get suppressed in the output.

I definitely would like feedback on if this was the right approach. But also, when I went to write an integration test for this, I couldn't get it working correctly. when incrementalTypsciptApi is on, i get warnings like:

{
   rawMessage: '\u001b[1m\u001b[31mERROR in \u001b[39m\u001b[22m\u001b[
1m\u001b[36mundefined(undefined,undefined)\u001b[39m\u001b[22m\u001b[1m\u001b[
31m:\u001b[39m\u001b[22m\n' +
    "\u001b[90mTS5055: \u001b[39mCannot write file '/test-context/src/lib/otherFunc.js' because it would overwrite input file.",
  message: '\u001b[1m\u001b[31mERROR in \u001b[39m\u001b[22m\u001b[1m\u001b[36mundefined(undefined,undefined)\u001b[39m\u001b[22m\u001b[1m\u001b[31m:\u001b[39m\u001b[22m\n' +
    "\u001b[90mTS5055: \u001b[39mCannot write file '/test-context/src/lib/otherFunc.js' because it would overwrite input file.",
  location: { line: undefined, character: undefined },
  file: undefined
}

[johnnyreilly]

Is it necessary to re-require ESLint here? We require it earlier in createEslinter. Is that no longer used with the new approach?

[jeffshaver]

No, this was an accidental add i think. My bigger questions are with how to test any of this since just adding a test caused tests to start failing.

[johnnyreilly]

The approach seems fine; you're using https://eslint.org/docs/developer-guide/nodejs-api#clienginegeterrorresults which looks to be a good call. Why the integration test is failing is mysterious... It seems to be an issue with writing to disk:

Cannot write file '/test-context/src/lib/otherFunc.js' because it would overwrite input file.

[johnnyreilly]

I thought my change (creating a new fixture) would fix the tests - it seems not 😢

The issue seems to be related to files in the test context not being cleaned up. Most perplexing.

[piotr-oles]

I'm closing it as I was able to release v5.0.0-alpha.1 version which allows you to specify issues predicates :)