fix(linter): fix false positives for no-control-regex

[camchenry]

• fixes linter: eslint(no-control-regex) warns \f as unexpected control character #10310

Addresses a TODO for no-control-regex now that we've fixed the spans for characters in the regular expression parser. This enables us to fix some false positives, because we can check if it was a \u or \x escape or not.

[camchenry]

• fix(linter): fix false positives for no-control-regex #10345 👈 (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 Instrumentation Performance Report

Merging #10345 will degrade performances by 3.32%

_{Comparing 04-09-fix_linter_fix_false_positives_for_no-control-regex_ (9f60552) with main (426f8cb)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 34 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⚡	formatter[antd.js]	7.9 ms	7.6 ms	+3.82%
❌	formatter[typescript.js]	7.2 ms	7.4 ms	-3.32%