[A11y] Track conflicts between auto disable heuristics + screen readers

When a screen reader is present, auto-disable should not trigger.
This tracks when that would happen so that we can improve the logic. Not that auto-disable doesn't actually activate because
the feature is turned off, but the heuristic is still being
checked, so we can get data on how much it conflicts with
screen reader usage now.

Note that there is some confusion between current methods and modes
related to screen readers, which are used for pretty much any
accessibility API consumer, and actual screen readers, which are
rare. In follow-ups we will clear this up with improved method
names for the general cases.

Follow-up: add heuristic for new focus and load complete logic,
and track those conflicts. For new heuristic logic, see
https://docs.google.com/document/d/1DlJn8PPE4towT0W4VknBqB04-SzFAz6yZ0graPc_xS8/edit?resourcekey=0-4sl6bwEWpA-1_ODsSOaWdg&tab=t.0#heading=h.xtpb10x0jn9z

NO_IFTTT=changing name of enum

Bug: none
Change-Id: I2897b67c8fa6a8db4bfaa94719f40de08b08e532
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6311309
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Mark Schillaci <mschillaci@google.com>
Cr-Commit-Position: refs/heads/main@{#1427454}