perf(linter/no_unescaped_entities): optimize string search and error generation

[overlookmotel]

#9777 made > or } in JSXText a parser error, so react/no_unescaped_entities rule can be simplified.

Speed it up a little by:

• Using raw field instead of slicing source.
• Iterating over the string as bytes, instead of chars.
• Using static strings for errors.

[overlookmotel]

• perf(linter/no_unescaped_entities): optimize string search and error generation #9832 👈 (View in Graphite)
• main

---

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.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Performance Report

Merging #9832 will not alter performance

_{Comparing 03-17-perf_linter_no_unescaped_entities_optimize_string_search_and_error_generation (2b65ed2) with main (6fc26db)}

Summary

✅ 33 untouched benchmarks

[Boshen]

Merge activity

• Mar 17, 10:09 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 17, 10:09 AM EDT: A user added this pull request to the Graphite merge queue.
• Mar 17, 10:21 AM EDT: A user merged this pull request with the Graphite merge queue.