feat(ast): compute max value that can be mapped to AstType

[camchenry]

• part of linter: dynamically skip running rules that do not have the relevant node types #12223

This adds an automatically generated usize which represents the largest variant that is contained in AstKind/AstType. In following PRs, this is used to create a set of bits that is exactly sized to the number of different AST node types there are.

[camchenry]

• perf(linter): add should_run based on node types (batch 3) #12231
• perf(linter): add should_run based on node types (batch 2) #12229
• perf(linter): add should_run based on node types (batch 1) #12228
• feat(semantic): add methods to check if AST contains any/all node types #12227
• feat(semantic): add set of AstType that exist in AST #12226
• feat(ast): compute max value that can be mapped to AstType #12225 👈 (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 #12225 will not alter performance

_{Comparing 07-11-feat_ast_compute_max_value_that_can_be_mapped_to_asttype_ (ea30a17) with main (242e721)}

Summary

✅ 34 untouched benchmarks