docs: fix malformed eslint config comments in rule examples

[fasttime]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

Tell us about your environment (npx eslint --env-info):

Node version: v21.6.0
npm version: v10.2.4
Local ESLint version: v9.0.0-alpha.2 (Currently used)
Global ESLint version: Not found
Operating System: darwin 23.3.0

What parser are you using (place an "X" next to just one item)?

[X] Default (Espree)
[ ] @typescript-eslint/parser
[ ] @babel/eslint-parser
[ ] vue-eslint-parser
[ ] @angular-eslint/template-parser
[ ] Other

Please show your full configuration:

Configuration

{
  "parserOptions": {
    "ecmaVersion": "latest",
    "sourceType": "module"
  }
}

What did you do? Please include the actual source code causing the issue.

/* eslint mentioned in this comment */

What did you expect to happen?

Block comments starting with eslint are treated as configuration comments for rules. When ESLint cannot parse them as such, it reports a fatal error (repro).

This fatal error should not be allowed to occur in rule examples because it makes the example code unparsable even if the syntax is correct. It should be caught by the tool that validates rule examples (tools/check-rule-examples.js).

What actually happened? Please include the actual, raw output from ESLint.

A rule example with a malformed eslint config comment can pass validation. We have two such examples in lines-around-comment, both fixed in this PR.

What changes did you make? (Give an overview)

• Fixed the rule examples in lines-around-comment by replacing eslint with jshint - another special word that doesn't trigger the rule.
• Extended the check-rule-examples tool to account for malformed eslint config comments when validating code.

Is there anything you'd like reviewers to focus on?

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	6f95b80
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/65be2788da4e9c0008688e43

[mdjermanovic]

This fatal error should not be allowed to occur in rule examples because it makes the example code unparsable even if the syntax is correct

Code with a malformed config comment is still parsed and rules are run. Linter just adds an error for the comment.

[mdjermanovic]

LGTM, thanks! Seems good to avoid these comments as the errors would show in the Playground.