refactor(rome_analyze): add the visitor and queryable trait

[leops]

Summary

This PR refactors the analysis infrastructure and introduces the concepts of Visitor and Queryable. The general goal of these changes is to let the analyzer support not just the linting use case, but also provide the infrastructure for all kind of analysis we may need to perform on top of the syntax tree to support formatting, compiling and various IDE features.

Visitor is the main new building block for the analyzer: in fact the analyzer is nothing more than an executor running a collection of visitors over a given syntax tree. All visitors are executed simultaneously and receive WalkEvent as the syntax tree is traversed, and may use the opportunity to mutate their own state, as well as mutably access the shared VisitorContext object.

This context holds a reference to the RuleRegistry through which the visitors may dispatch QueryMatch objects to trigger the rules associated with a certain Queryable type: for instance rome_analyze defines a SyntaxVisitor that dispatches an Ast<T> query match for each node it enters, which is the query type used by all currently existing lint rules as they all currently work on AST nodes.

The PR also introduces a new merge_node_visitors macro that creates a single struct implementing Visitor over a collection of type implementing the NodeVisitor helper trait. Unlike the global Visitor, node visitors are transient: they get instantiated when the traversal enters the corresponding node and destroyed when the node is exited. They are intended as a building blocks for creating and managing the state of complex visitors by allowing the implementation to be split over multiple smaller components.

Test Plan

TODO: Despite being more open-ended the components of this infrastructure are still tied together quite tightly, and this doesn't really allow writing tests for individual components. It should be possible to improve this by at least decoupling the emission of query matches by the visitors from the execution of rules matching on these queries

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	fc4f882
Status:	✅  Deploy successful!
Preview URL:	https://dbbdb1b0.tools-8rn.pages.dev
Branch Preview URL:	https://refactor-analyze-visitor.tools-8rn.pages.dev

View logs

[github-actions]

Playground for commit a10b166

[github-actions]

Parser conformance results on ubuntu-latest

js/262

Test result	main count	This PR count	Difference
Total	45878	45878	0
Passed	44938	44938	0
Failed	940	940	0
Panics	0	0	0
Coverage	97.95%	97.95%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	39	39	0
Passed	36	36	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.31%	92.31%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	5946	5946	0
Passed	388	388	0
Failed	5558	5558	0
Panics	0	0	0
Coverage	6.53%	6.53%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	588	588	0
Passed	519	519	0
Failed	69	69	0
Panics	0	0	0
Coverage	88.27%	88.27%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	16257	16257	0
Passed	12393	12393	0
Failed	3864	3864	0
Panics	0	0	0
Coverage	76.23%	76.23%	0.00%

[ematipico]

doc?

[leops]

This is basically just a "newtype" struct that wraps an AstNode type N to implement Queryable on it, this is a common pattern in Rust to get around the orphan rule