feat: resolve analytics label from associated <label for> element

[gethinwebster]

Description

getLabelFromElement now resolves the text of an associated label[for="id"] when the element has no accessible name of its own. Resolution order becomes: aria-label → aria-labelledby → <label for> → textContent.

Motivation

Autocapture analytics can't resolve a label for controls whose accessible name is bound only via an external <label for> (rather than an aria-* attribute or child text). AbstractSwitch already points its detail.label selector at the native <input> when used without a label prop — but that input has no aria/text of its own, so the label resolved to ''. The most visible case is CollectionPreferences visible-content column toggles, which currently emit select/deselect events with an empty label.

Testing

• Added unit tests: resolves via <label for>; aria-label still takes precedence.
• npm run test:unit (analytics-metadata), npm run build, npm run lint all pass.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.00%. Comparing base (cce49df) to head (9e877b7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #228   +/-   ##
=======================================
  Coverage   99.00%   99.00%           
=======================================
  Files          44       44           
  Lines        1307     1313    +6     
  Branches      363      364    +1     
=======================================
+ Hits         1294     1300    +6     
  Misses         12       12           
  Partials        1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.