docs: publish native Android benchmark pilot

[janicduplessis]

Description

The benchmark page still lists native Android as pending, although a matching Stim/control pair now passed independent audits and cleanup. The runs took 151.6 and 153.4 seconds, so this is near parity, not evidence of a meaningful speed advantage.

Solution

Publish the accepted Android timings and proof images alongside the native iOS and macOS pilots. Keep the one-pair and total-task-time limitations visible, with Android labeled “Near parity.”

Test plan

Export validation passed for accepted audits, evidence hashes, matching protocols, and completed cleanup. Verified the built page shows all three native platforms and both Android proof images. Repository checks passed after updating the rendering test's obsolete Android-absent assertion; affected rendering/export tests and runtime checks passed.

Normal PR CI and the website CI build passed. An additional manual full-Windows run failed in unchanged CLI/core tests; 13 failures recur in the nightly baseline, with one additional existing cancellation-test timeout. Tracked in #3697. The merge gate is failing on that run; publication awaits a maintainer exception or Windows fixes.

Fixes #3695.

[janicduplessis]

Maintainer explicitly approved merging this website-only PR with the documented full-Windows CI exception in the task conversation. Normal PR CI, website build, and independent review passed at 8ba4270. Unchanged Windows failures remain tracked in #3697; this exception does not mark them fixed.