Add Android Emulator dependencies installation step to Android workflow

[Copilot]

Summary

Adds the "Install Android Emulator dependencies" step to the run-emulator job in _android.yml. This installs required system libraries (libX11-xcb, libxcb, pulseaudio-libs, nss, libXcomposite, libXcursor, libXi, libXtst, alsa-lib, mesa-libGL, mesa-dri-drivers) via dnf on the linux.24xl.spr-metal runner before the Android emulator runs.

Mirrors the change from executorch-examples PR #148.

Test plan

• Validated YAML syntax
• CI will validate the workflow runs correctly

Original prompt

add this step https://github.com/meta-pytorch/executorch-examples/pull/148/files#diff-7eae48a8a0554f29a0ac912968e167d7ca50fa1306864dd3a8f4db44c667f9c4R58-R69 before we run https://github.com/pytorch/executorch/blob/main/.github/workflows/_android.yml#L55
i am testing on my side as well

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16612

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 1 Cancelled Job

As of commit 5970d5d with merge base a0ba28e ():

NEW FAILURE - The following job has failed:

• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t f19f446ab4b7dadf28c6385e6ea5889b5087d7bccd65d51f36357c22b21a14ca /exec failed with exit code 1

CANCELLED JOB - The following job was cancelled. Please retry:

• pull / test-samsung-models-linux / linux-job (gh)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.