Fake time pumped at the end of each capture, with the tree still mounted,
so one-shot timers started by the screen or by explore taps (snack bars,
fake-backend delays) fire; flutter_test fails a test ending with a
pending timer. Periodic timers never drain: those are leaks to fix.
Locales to capture (BCP 47, e.g. [en, it, ar]); the first is the
default and gets no id suffix. Applied through the platform locale, so
apps that force MaterialApp.locale ignore it.
When > 0, after the settle pumps the harness waits this many real
milliseconds inside tester.runAsync and pumps again, so that real
I/O (HTTP, which flutter_test answers with 400, file reads) can
complete and screens reach their loaded/error state instead of
spinning forever in the fake-async zone.