Fix flaky AnkiDroidJsAPITest on Windows CI

[kevs-mist]

---

Purpose / Description
AnkiDroidJsAPITest flakes on Windows CI with UncompletedCoroutinesError: After waiting for 1m, the test body did not run to completion. On slow Windows runners, startReviewer() and advanceRobolectricLooper() consume most of the default 1-minute runTest budget before any assertions run, causing sporadic timeouts.

Fixes

• Fixes Refactor NoteEditor to use changeNoteType dialog #20377

Approach

• Added an explicit 5.minutes timeout constant (TEST_TIMEOUT) to all runTest calls in the class, giving adequate headroom on slow CI runners while still catching genuine hangs
• Fixed ankiJsUiTest which was annotated with @override instead of @Test, causing it to be silently skipped by JUnit and never actually run

How Has This Been Tested?
Verified locally that TEST_TIMEOUT is present in the file. The flake is infrastructure-dependent (Windows CI runner slowness) so cannot be fully reproduced locally, but the fix directly addresses the timeout budget issue identified in the CI logs.

Learning
The default runTest timeout of 1 minute is documented in kotlinx.coroutines.test — it is intentionally tight for unit tests but insufficient for Robolectric tests that spin up a full Reviewer activity. See [kotlinx.coroutines TestBuilders docs](https://kotlinx.github.io/kotlinx.coroutines/kotlinx-coroutines-test/kotlinx.coroutines.test/run-test.html).

---

Checklist:

• Check the first three boxes ✅
• Leave the UI and accessibility ones unchecked (no UI changes)

[david-allison]

This doesn't look correct, especially as it hasn't reproduced the issue. Tests should not be taking 1 minute to execute, and this doesn't deal with the root cause.

I'll also note our AI policy: unsure if this is LLM-generated: https://github.com/ankidroid/Anki-Android/blob/main/AI_POLICY.md

[kevs-mist]

I am really sorry, sir. I was not able to understand the issue. I can improve it further and generate a new PR.

[david-allison]

Don't worry if you can't understand it, some issues aren't easy, and this one will likely stump me for a while (as I don't have a sufficiently powerful windows machine).

Better to focus on a small number of high quality PRs, there's no need to rush here!