feat(rome_analyzer): ARIA query

[ematipico]

Summary

This is the first step towards having some APIs to get information about ARIA properties and ARIA roles.

What this PR does

The amount of metadata around ARIA properties and ARIA roles is very big, and it can get bigger with time, here's what we need to eventually support:

• https://github.com/rome/tools/blob/archived-js/internal/compiler/lint/utils/aria/ariaPropsMap.ts
• https://github.com/rome/tools/blob/archived-js/internal/compiler/lint/utils/aria/ariaRolesMap.ts

This is a list of the metadata that I once created when I implemented the ARIA rules in rome classic. This metadata was copied from the existing eslint-plugin-jsx-a11y, which was a crafted data list from https://www.w3.org/TR/wai-aria-1.1

Considering the amount of information, I thought we could opt-in this metadata using the same query system we use for the semantic model. Fortunately, rules that involve ARIA should not involve the semantic model, so this works perfectly for us.

There's some generated code in an attempt to make the metadata small, but if you have some enhancements, please share!

I could plan to add the generated code using build.rs, but not in this PR (I tried before but I had some issues at compile time).

I also added a new API to the RuleDiagnostic, called note_list. You can see the results in the diagnostics.

This PR adds new rules that use the newly added APIs:

• useAriaProps
• useAriaPropTypes

The two rules are not exhaustive and that's the plan for this PR. I wanted to at least add a couple of failing cases to get a feeling of how the APIs should be crafted.

What this PR doesn't do

• it doesn't attempt to add ALL the metadata of all the ARIA roles and ARIA properties;
• it doesn't attempt to document the newly added rules;
• it doesn't attempt to make the newly added rules exhaustive;
• it doesn't attempt to try to add all possible APIs that we might need in the future, the intent is the crate new APIs with time while we implement new rules;

Test Plan

There are some doc tests to make sure that we don't overflow the stack, considering that we directly access an array. I also added snapshots for the new rules.

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Name	Link
🔨 Latest commit	a672521
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/6384d7bcc5a1f600091b2bdf

[github-actions]

Parser conformance results on ubuntu-latest

js/262

Test result	main count	This PR count	Difference
Total	45879	45879	0
Passed	44936	44936	0
Failed	943	943	0
Panics	0	0	0
Coverage	97.94%	97.94%	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	1757	1757	0
Failed	4189	4189	0
Panics	0	0	0
Coverage	29.55%	29.55%	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	12397	12397	0
Failed	3860	3860	0
Panics	0	0	0
Coverage	76.26%	76.26%	0.00%

[MichaReiser]

An alternative to having a service could be to use lazy_static and expose the roles and properties globally.