fix(anki-26.09): defer reloading the page until 'Save & Optimize' has been handled

[david-allison]

Note

Assisted-by: GPT-6

Purpose / Description

In 26.09, Save & Optimize starts a save, then reloads. This can interrupt the response to AnkiDroid and broke one of our instrumentation tests.

This appears to be a legitimate failure due to a missing await: https://github.com/ankitects/anki/blob/41d7464c9b673e2aa15f76daa76d77ee110d7533/ts/routes/deck-options/FsrsOptions.svelte#L352-L353

Run python3 .github/report_emulator_test_failures.py AnkiDroid/build/outputs/androidTest-results/connected adb-log.txt
Error: com.ichi2.anki.pages.DeckOptionsTest.optimizingAllPresetsSavesAndReloadsOptions
java.lang.AssertionError: options did not reload after optimization
	at org.junit.Assert.fail(Assert.java:89)
	at kotlin.test.junit.JUnitAsserter.fail(JUnitSupport.kt:56)
	at kotlin.test.AssertionsKt__AssertionsKt.fail(Assertions.kt:564)
	at kotlin.test.AssertionsKt.fail(Unknown Source:1)
	at com.ichi2.anki.testutil.WaitUtilsKt.waitUntil-KLykuaI(WaitUtils.kt:31)
	at com.ichi2.anki.pages.DeckOptionsTest.optimizingAllPresetsSavesAndReloadsOptions$lambda$0(DeckOptionsTest.kt:79)
	at com.ichi2.anki.pages.DeckOptionsTest.$r8$lambda$FG7CRc2X4s57kecsqD6fJ-RL8Ro(DeckOptionsTest.kt:0)
	at com.ichi2.anki.pages.DeckOptionsTest$$ExternalSyntheticLambda18.invoke(R8$$SyntheticClass:0)
	at com.ichi2.anki.pages.DeckOptionsTest.withDeckOptions(DeckOptionsTest.kt:125)
	at com.ichi2.anki.pages.DeckOptionsTest.optimizingAllPresetsSavesAndReloadsOptions(DeckOptionsTest.kt:72)
Skipped tests (9)

• if we get a failure; we don't want to navigate away as that loses state
• if we navigate during the frontend reading the body, it is treated as an error

Fixes

• Unblocks feat(backend): upgrade to Anki 26.09.3  #22154
• Part of Integrate Anki 26.09 #21926

Approach

We hook into the save request, deferring a page reload until the frontend has handled the successful response.

We work around this by hooking into blob() and reporting this to AnkiDroid. After the read occurred, it's safe to reload (even if this discards the UI handling of the response - we were reloading anyway).

How Has This Been Tested?

Heavily unit tested, the existing instrumented test now passes.

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

[mikehardy]

LGTM — after adversarial review + local CI-parity (lint/unit/emulator on API36_GAPI_PS16K) on a rebase onto current main.