[feat] check noninteractive roles on interactive elements

[anthonylegoas]

Fixes no-interactive-element-to-noninteractive-role of #820

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with npm test and lint the project with npm run lint

[Conduitry]

Thanks the PR! When I'm looking at the ESLint plugin's implementation (here), though, it looks like there's a bit more going on than is listed in the documentation for this rule. Have you looked at their implementation, and do you think there's anything else we might want to do besides checking for this set of roles on this set of elements?

[anthonylegoas]

Indeed there are more non-interactive aria-roles than those listed in the documentation.
I pushed another implementation, using aria-query (used in eslint-plugin-jsx-a11y), based on the fact that the interactive roles are the widget roles.
I also ignored the abstract roles.

and do you think there's anything else we might want to do besides checking for this set of roles on this set of elements?

According to the Aria 1.1 specification there are many things we can do about aria-role checks. I'm going to do more PRs.

[Conduitry]

This has been released in 3.50.0. Thank you!