fix: ESLint linter expects different output

[pavkam]

This PR fixes ESLint linter parsing. Tested on ESLint v8.42.0.

The expected format is:

[
  {
    "filePath": "<full_file_path>",
    "messages": [
      {
        "ruleId": "simple-import-sort/imports",
        "severity": 1,
        "message": "Run autofix to sort these imports!",
        "line": 1,
        "column": 1,
        "nodeType": null,
        "messageId": "sort",
        "endLine": 14,
        "endColumn": 45,
        "fix": {
          "range": [0, 456],
          "text": "<... fix ...>"
        }
      }
    ],
    "suppressedMessages": [],
    "errorCount": 0,
    "fatalErrorCount": 0,
    "warningCount": 1,
    "fixableErrorCount": 0,
    "fixableWarningCount": 1,
    "source": "<... original ...>",
    "usedDeprecatedRules": []
  }
]

[sQVe]

👋🏼,

Sorry about the issue @pavkam. I have created a PR that fixes the issues I introduced for the eslint and eslint_d linters. The test is also updated with the correct JSON output.

See #416.