docs(linter): Use backticks for code elements across more rule diagnostics

[connorshea]

Improves the consistency of diagnostic formatting in 30ish rules, and improves the diagnostic messages in editors that render markdown, plus makes it clearer which parts refer to code for end-users, even with the raw text.

-lso adjust the phrasing of some diagnostics slightly.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[Copilot]

Pull request overview

This PR improves the consistency and readability of diagnostic messages across approximately 30 linter rules by wrapping code elements (properties, functions, HTML elements, JSDoc tags) in backticks. This formatting enhancement makes diagnostics render better in Markdown-aware editors and clearly distinguishes code elements from natural language text.

Key Changes:

• Added backticks around JSX/HTML elements (e.g., <th>, <marquee>)
• Added backticks around JavaScript identifiers and properties (e.g., tabIndex, onFocus)
• Added backticks around JSDoc tags (e.g., @property, @access)
• Minor grammar improvements (e.g., capitalizing "Does" in help messages, "A module" instead of "module")

Reviewed changes

Copilot reviewed 59 out of 59 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
Multiple .snap files	Updated snapshot tests to reflect new diagnostic message formatting with backticks
jsx_a11y/*.rs	Added backticks to code elements in diagnostic messages for accessibility rules
jsdoc/*.rs	Added backticks to JSDoc tag names in diagnostic messages
import/*.rs	Added backticks to code elements and minor grammar improvements
eslint/*.rs	Added backticks to function names and keywords in diagnostic messages

The changes are consistent, well-formatted, and improve the user experience by making diagnostic messages clearer and more professional. All modifications are limited to string literals in diagnostic messages and their corresponding test snapshots, with no functional code changes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codspeed-hq]

CodSpeed Performance Report

Merging #15958 will not alter performance

_{Comparing diagnostic-consistency (fe37699) with main (a21f9e4)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

1. No successful run was found on main (15365c9) during the generation of this report, so a21f9e4 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[camc314]

Merge activity

• Nov 22, 11:14 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 22, 11:14 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Nov 22, 11:21 AM UTC: Merged by the Graphite merge queue.