Add documentation for Windows ARM device limitations with Android emulators

[Copilot]

This PR addresses the lack of documentation around Android emulator support on Windows ARM devices by adding comprehensive guidance across key documentation files.

Changes Made

Hardware Acceleration Guide (docs/android/emulator/hardware-acceleration.md):

• Added new "Windows ARM device limitations" section explaining x64 architecture requirement
• Lists specific affected devices (Surface Pro X, Surface Pro 9 5G/ARM variant, other Snapdragon-based Windows devices)
• Provides practical alternatives including physical device debugging, cloud environments, and Windows Subsystem for Android

Installation Guide (docs/get-started/installation.md):

• Added IMPORTANT admonition during Android emulator setup to warn users upfront about ARM device incompatibility
• Directs users to physical device debugging as an alternative

Troubleshooting Guide (docs/android/emulator/troubleshooting.md):

• Enhanced performance issues section to include Windows ARM device incompatibility as a cause
• Added dedicated "Windows ARM device compatibility" section with specific troubleshooting guidance
• Explains architecture incompatibility and provides clear alternatives

Problem Addressed

The Android emulator requires x64 processor architecture as documented in Google's Android Emulator requirements. However, this limitation wasn't clearly documented in the .NET MAUI documentation, leading to confusion for developers using Windows ARM devices like Surface Pro X who encounter emulator startup issues or performance problems.

Result

Developers using Windows ARM devices now have clear documentation explaining:

• Why the Android emulator doesn't work on their devices
• What specific devices are affected
• What alternatives are available for Android development and testing

The documentation follows existing patterns, maintains proper cross-references, and provides actionable guidance for affected users.

Fixes #2394.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Internal previews

📄 File	🔗 Preview link
docs/android/emulator/hardware-acceleration.md	docs/android/emulator/hardware-acceleration
docs/android/emulator/troubleshooting.md	docs/android/emulator/troubleshooting
docs/get-started/installation.md	docs/get-started/installation

[learn-build-service-prod]

Learn Build status updates of commit cf80948:

✅ Validation status: passed

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 200e399:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/android/emulator/hardware-acceleration.md	✅Succeeded	View (>=net-maui-8.0)
docs/android/emulator/troubleshooting.md	✅Succeeded	View (>=net-maui-8.0)
docs/get-started/installation.md	✅Succeeded	View (>=net-maui-8.0)

For more details, please refer to the build report.