Aria value text debounce causes unreproducibility

[samreid]

In https://github.com/phetsims/turing/issues/9 I observed that aria value text were often inconsistent during deterministic fuzzing. For instance:

totality (main) % npm run pure-refactor-test

> pure-refactor-test
> bash perennial-alias/bin/sage run turing/js/snapshot-shas.ts compare

Comparing against /Users/reids/phet/totality/_temp/snapshot-shas/quantum-wave-interference.yaml
Baseline: 524a09b5ae4110aa2974922315f6fcbcddf152fd captured 2026-05-22T03:01:18.214Z
Generating PhET-iO API fingerprint for quantum-wave-interference...
Capturing whole-sim (brand=phet&ea)...
Capturing screens-1 (brand=phet&ea&screens=1)...
Capturing screens-2 (brand=phet&ea&screens=2)...
Capturing screens-3 (brand=phet&ea&screens=3)...
http://localhost/quantum-wave-interference/quantum-wave-interference_en.html?ea&brand=phet-io&phetioStandalone&phetioPrintAPI&randomSeed=332211&webgl=false
http://localhost/aqua/html/snapshot-comparison.html?repos=quantum-wave-interference&simSeed=4&simWidth=256&simHeight=192&simQueryParameters=brand%3Dphet%26ea&numFrames=10&compareDescription=true&allowAriaValueDebounce=false
http://localhost/aqua/html/snapshot-comparison.html?repos=quantum-wave-interference&simSeed=4&simWidth=256&simHeight=192&simQueryParameters=brand%3Dphet%26ea%26screens%3D1&numFrames=10&compareDescription=true&allowAriaValueDebounce=false
http://localhost/aqua/html/snapshot-comparison.html?repos=quantum-wave-interference&simSeed=4&simWidth=256&simHeight=192&simQueryParameters=brand%3Dphet%26ea%26screens%3D2&numFrames=10&compareDescription=true&allowAriaValueDebounce=false
http://localhost/aqua/html/snapshot-comparison.html?repos=quantum-wave-interference&simSeed=4&simWidth=256&simHeight=192&simQueryParameters=brand%3Dphet%26ea%26screens%3D3&numFrames=10&compareDescription=true&allowAriaValueDebounce=false
  2fb7e246 frames=10 elapsed=4544ms
  5bc449e6 frames=10 elapsed=3290ms
  54c3f00f frames=10 elapsed=3410ms
  ac3d7d3e frames=10 elapsed=4146ms

Snapshot SHA comparison failed:
- screens-3: hash-changed
  baseline: 5de71008ba88803d8297eccc4e6f0957
  current:  ac3d7d3eb379127b4e073ad5934dc470
  frames: baseline=10, current=10
- screens-3/pdom: text-changed
  baseline file: _temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-baseline-2026-05-22T03-02-34-513Z.html
  current file:  _temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-current-2026-05-22T03-02-34-513Z.html
  diff -u '_temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-baseline-2026-05-22T03-02-34-513Z.html' '_temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-current-2026-05-22T03-02-34-513Z.html'
totality (main) % npm run pure-refactor-test
totality (main) %   diff -u '_temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-baseline-2026-05-22T03-02-34-513Z.html' '_temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-current-2026-05-22T03-02-34-513Z.html'
--- _temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-baseline-2026-05-22T03-02-34-513Z.html	2026-05-21 21:02:34
+++ _temp/snapshot-shas/description-diffs/quantum-wave-interference-screens-3-pdom-current-2026-05-22T03-02-34-513Z.html	2026-05-21 21:02:34
@@ -570,7 +570,7 @@
               <p class="a11y-pdom-element" data-focusable="false" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-867-861" id="display1-description-15-29-100-107-103-1256-1132-1017-1010-1009-867-861">Choose graph or screen representation for data analysis.</p>
             </div>
             <label class="a11y-pdom-element" data-focusable="false" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" for="display1-primary-15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" id="display1-label-15-29-100-107-103-1256-1132-1017-1010-1009-1008-997">Screen Brightness</label>
-            <input aria-orientation="horizontal" aria-valuenow="0.125" aria-valuetext="0.125" class="a11y-pdom-element" data-focusable="true" data-phet-io-id="quantumWaveInterference.singleParticlesScreen.view.brightnessSlider" data-phet-node-type="HSlider" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" disabled="" id="display1-primary-15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" max="0.25" min="0" step="any" type="range"></input>
+            <input aria-orientation="horizontal" aria-valuenow="0.125" aria-valuetext="50 percent" class="a11y-pdom-element" data-focusable="true" data-phet-io-id="quantumWaveInterference.singleParticlesScreen.view.brightnessSlider" data-phet-node-type="HSlider" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" disabled="" id="display1-primary-15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" max="0.25" min="0" step="any" type="range"></input>
             <p class="a11y-pdom-element" data-focusable="false" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-1008-997" id="display1-description-15-29-100-107-103-1256-1132-1017-1010-1009-1008-997">Adjust brightness to optimize visual analysis of pattern on detector screen.</p>
             <button class="a11y-pdom-element" data-focusable="true" data-phet-io-id="quantumWaveInterference.singleParticlesScreen.view.snapshotButton" data-phet-node-type="SnapshotButton" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-992-991-976" disabled="" id="display1-primary-15-29-100-107-103-1256-1132-1017-1010-1009-992-991-976">Take Snapshot</button>
             <p class="a11y-pdom-element" data-focusable="false" data-unique-id="15-29-100-107-103-1256-1132-1017-1010-1009-992-991-976" id="display1-description-15-29-100-107-103-1256-1132-1017-1010-1009-992-991-976">Capture and store up to 4 snapshots of detector screen pattern.</p>

I found there is a nondeterministic ordering when using aria value text debounce, which was introduced in #971

So I would like to add a query parameter that our tooling can use when deterministic values are necessary here.

[samreid]

I considered putting this in a feature branch, but (a) the reviewer is out tomorrow, (b) I would like to leverage this for the tooling in https://github.com/phetsims/turing/issues/9 right away (not in a branch off of the feature branch, which would be difficult to share with my subteam), and (c) by its nature it is already behind a "feature flag", so I will bring it to main and request review here.