ci(emulator): disable ART metrics reporting

[david-allison]

Note

Assisted-by: Claude Fable 5.1

Purpose / Description

On the 16 KB page size image, ART's first statsd metrics report probes userfaultfd() from inside WebView's sandboxed renderer.

Chromium's renderer seccomp policy denies the syscall and kills the renderer.

Fixes

• Fixes flaky test: raisedDoubleTapIntervalUnlocksParametersWithSlowerTaps #21740
• Fixes Flaky test: defaultDoubleTapIntervalKeepsPageTimeout #21756
• Fixes flaky emulator test #21828

Approach

setprop persist.device_config.runtime_native.metrics.write-to-statsd false

How Has This Been Tested?

⚠️ This will only take effect when merged. I was unable to test locally (insufficient space)

Learning

https://github.com/ankidroid/Anki-Android/actions/runs/33988451423/artifacts/9976165404

20:12:47.774 TestRunner: started: raisedDoubleTapIntervalUnlocksParametersWithSlowerTaps
20:12:49.409 DeckOptions: WebView ready to receive input
20:12:49.858 cr_seccomp: **CRASHING**:seccomp-bpf failure in syscall
20:12:49.858 cr_seccomp: nr=0x143 arg1=0x80001 arg2=0x10ff arg3=0x0 arg4=0x7ff5c0fcc080
20:12:50.984 DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
             Page size: 16384 bytes
             pid: 6848, tid: 6849, name: Metrics Backgro  >>> com.google.android.webview:sandboxed_process0 <<<
             #03 libc.so (syscall+23)
             #04 libart.so (art::KernelSupportsUffd()+61)
             #05 libart.so (art::gc::collector::MarkCompact::GetUffdAndMinorFault()+46)
             #06 libart.so (art::metrics::StatsdBackend::ReportCounter(...)+132)
             #08 libart.so (art::metrics::MetricsReporter::ReportMetrics()+442)
20:12:51.016 SafeWebViewClient: onRenderProcessGone (didCrash true)
20:12:51.531 DeckOptions: WebView ready to receive input        <- page reloaded, test's JS state gone
20:12:59.818 TestRunner: failed: raisedDoubleTapIntervalUnlocksParametersWithSlowerTaps
             java.lang.AssertionError: tap sequence did not complete

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner