refactor(linter): remove run_on_symbol

[camchenry]

• closes Linter: remove run_on_symbol? #14644

Previous PRs removed most usage of this run function, and this migrates the rest to use run_once. The motivation for this is not performance (this is likely a slight regression, actually), but should be a slight benefit to binary size and general maintenance. We now only have 3 ways of running lint rules, which makes the linter runtime code simpler.

[codspeed-hq]

CodSpeed Performance Report

Merging #14610 will not alter performance

_{Comparing 10-14-refactor_linter_remove_run_on_symbol_ (90f5f89) with main (676ee99)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

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

2. 33 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. ↩

[camchenry]

• perf(linter): update linter codegen to support wildcard with empty tuple #14611
• refactor(linter): remove run_on_symbol #14610 👈 (View in Graphite)
• perf(linter): update no-const-assign to run on nodes instead of symbols #14609
• perf(linter): run next/no-duplicate-head on nodes instead of symbols #14607
• perf(linter): switch no-param-reassign to run on nodes #14604
• perf(linter): run no-class-assign on class nodes instead of symbols #14578 : 1 other dependent PR (#14579 )
• 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.

[graphite-app]

Merge activity

• Oct 15, 9:10 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Oct 15, 9:23 AM UTC: Merged by the Graphite merge queue.