Update @vardot/varbase-e2e to 2.0.7 and gate the full AA accessibility audit

Problem/Motivation

@vardot/varbase-e2e 2.0.7 turns the impact gate into a ladder: no serious accessibility violations now fails on critical as well, and a new any-impact gate exists. It also adds a one-step full check, element-scoped rule assertions, and probes that skip what assistive technology cannot reach.

Educare is pinned to ^2.0.6, so none of that applies here yet.

Separately, tests/features/07-quality/07-01-accessibility.feature carries a note saying heading-order is deliberately not gated, because card titles hardcoded a deep heading level. The note says to gate the full AA audit once heading levels are decoupled from visual size. #3625237 and #3625285 did exactly that, so the exemption has outlived its reason.

Proposed resolution

• Bump @vardot/varbase-e2e to ^2.0.7.
• Retire the heading-order exemption and gate a full AA audit on all 14 shipped pages.
• Add the coverage 2.0.7 makes possible: the one-step full check, an any-impact gate on the home page, the structural landmarks a screen-reader user navigates by, and rule assertions scoped to the components Educare owns.

Verified on a fresh Drupal CMS install of the recipe: the 07-quality bucket is 95 scenarios, 95 passed.

One 2.0.7 step is deliberately not adopted. required fields should be consistently marked asks for both a native required attribute and aria-required="true" on the same field. The contact webform sets the native attribute only, which is not a WCAG failure and which axe does not flag, since a native required is already exposed to assistive technology. Gating on it would report a false positive.

Remaining tasks

✅ Update to 2.0.7
✅ Retire the heading-order exemption and gate the full AA audit
✅ Add the new accessibility coverage
✅ Prove the suite green on a fresh install
➖ Review
➖ Release

User interface changes

None. Test-only.

API changes

None.

Data model changes

None.