test(e2e): freeze Settings' and Downloads' keyboard reach

A component test sees the markup; only this tier sees that the control
is reachable through the app's own tab order. Also stops
failure-voice.spec assuming the Libraries section starts collapsed — it
is the one section that starts open now, so a blind click on the
disclosure closed it and the rest of the spec ran against a hidden row.

e2e/specs/failure-voice.spec.ts

@@ -33,11 +33,16 @@ test.describe('a failed binding says so', () => {
 
     const page = app.locator('config-page');
 
-    // Config sections start collapsed.
-    await page
+    // Libraries is the one section that starts expanded (H-22), so ask
+    // the disclosure what state it is in rather than assuming one — a
+    // blind click used to expand it and now collapses it.
+    const disclosure = page
       .locator('config-section[heading="Libraries"]')
-      .locator('.header')
-      .click();
+      .locator('.header');
+
+    if ((await disclosure.getAttribute('aria-expanded')) === 'false') {
+      await disclosure.click();
+    }
 
     // Renaming the decoy to its own name is a no-op the backend
     // accepts, so the rename has to happen on the other row.