fix(template-require-mandatory-role-attributes): use axobject-query for semantic-role exemptions

[johanrd]

Premise

Per WAI-ARIA APG and HTML-AAM, a native HTML element that implements a given ARIA role implicitly supplies that role's required ARIA state. Classic example: <input type="checkbox" role="switch"> — the native checked attribute provides the aria-checked state that role="switch" requires. Authors shouldn't need to add aria-checked redundantly.

Problem

The rule flags any element with a role missing required ARIA attributes, including patterns where the native element already provides the state. <input type="checkbox" role="switch"> is flagged for missing aria-checked — a documented false positive.

Fix

Consult axobject-query's elementAXObjects + AXObjectRoles maps to determine when a native element satisfies a given role, mirroring eslint-plugin-jsx-a11y's isSemanticRoleElement. When the pair matches, skip the missing-attribute check for that role.

Adds axobject-query@^4.1.0 as a direct dependency. It's already installed as a transitive dep across the ecosystem; elevates to first-class.

Coverage (non-exhaustive)

Element	Role	Required ARIA supplied by
<input type="checkbox">	checkbox, switch	native checked state
<input type="radio">	radio	native checked state
<input type="range">	slider	native value / min / max
<input type="number">	spinbutton	native value (no required ARIA)
<input type="text">	textbox	no required ARIA
<input type="search">	searchbox	no required ARIA

Both angle-bracket syntax (<input type="checkbox" role="switch">) and the classic {{input type="checkbox" role="switch"}} helper are handled.

Undocumented pairings still flag

<input type="checkbox" role="menuitemcheckbox"> / <input type="radio" role="menuitemradio"> etc. — axobject-query doesn't list these, so they remain flagged for missing aria-checked. Matches jsx-a11y and angular-eslint behavior.

Why not keep the hand-list?

An earlier revision of this PR hand-maintained a 3-entry {input type}:{role} whitelist. Audit-time review showed:

• Even the 3 entries had a factual error: the earlier 5-entry version cited axobject-query for menuitemcheckbox/menuitemradio pairings that axobject-query doesn't actually encode. A hand-list encodes the maintainer's (imperfect) understanding of the library's data; using the library directly eliminates the drift class.
• axobject-query's coverage is strictly broader than what a hand-list would capture (see table above). A hand-list reduces false positives for 3 patterns; axobject-query reduces them for many more.
• jsx-a11y and @angular-eslint/template already use this approach; aligning removes a documented parity gap.

Prior art

Plugin	Rule	Mechanism
jsx-a11y	role-has-required-aria-props	isSemanticRoleElement(type, attributes) via axobject-query's elementAXObjects
@angular-eslint/template	role-has-required-aria	Same helper, backed by axobject-query
vuejs-accessibility	role-has-required-aria-props	Hardcoded carve-out for {role: switch, type: checkbox} only — much narrower than axobject-query
lit-a11y	role-has-required-aria-attrs	No semantic-role exemption at all

This PR aligns with jsx-a11y / angular-eslint on the axobject-query-backed approach. vue-a11y's narrower carve-out and lit-a11y's no-exemption behavior are documented divergences.

What this PR does not fix

Role-token case-insensitivity at the rule level — <input type="checkbox" role="SWITCH"> is silently ignored (aria-query's roles.get(role) is case-sensitive, so the rule short-circuits to null before reaching the isSemanticRoleElement check). That rule-wide gap is addressed in #2728.

Audit fixture

Translated peer-plugin test fixture at tests/audit/role-has-required-aria/peer-parity.js. Not wired into the default test run.