ci: Address stalling Android E2E test tasks

[dcalhoun]

What?

Address recently indefinite hanging that occurs while terminating the emulator for the Android end-to-end test CI tasks.

Why?

The CI tasks never complete, so a successful test suite run is never reported, which blocks the pull request status and causes confusion.

How?

Remove the recommended AVD cache, as it appears its presence can cause indefinite hangs while terminating the emulator, as referenced several times in the reactivecircus/android-emulator-runner issue tracker:

• Runner action hangs after killing emulator with stop: not implemented ReactiveCircus/android-emulator-runner#385
• Running emulator with cache on multiple jobs causes the jobs to hang. ReactiveCircus/android-emulator-runner#362
• Android SDK API 29 constant timeout after successful run (also sometimes 26 and 28) ReactiveCircus/android-emulator-runner#373
• Job hangs after UI testing is terminated ReactiveCircus/android-emulator-runner#381

It is possible that removing the AVD cache is somewhat of an ineffective fix—temporarily solving the issue in the form of removing a problematic cache—but, given numerous other people report the AVD cache as problematic, I figure removing the AVD cache is worth a try.

Testing Instructions

N/A, no user-facing changes.

Testing Instructions for Keyboard

N/A, no user-facing changes.

Screenshots or screencast

N/A, no user-facing changes.

[github-actions]

Flaky tests detected in cfa7b81.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11692403211
📝 Reported issues:

• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dcalhoun <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.