Beta v5.0.3 Android guest color inversion bug (RGB/BGR byte mismatch)

**Describe the issue** When booting an Android 9 OS by osy old vms in UTM Beta v5.0.3, the entire display renders with heavily distorted/inverted colors (turning standard backgrounds and UI elements into a stark purple tint). This is entirely a color-space mapping or pixel-format byte order issue (e.g., QEMU interpreting RGB source frames as BGR format on the host surface)
A clear and concise description of what the issue is. **BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.**

**Configuration (required)**
* UTM Version: beta v5.0.3
* OS Version: 26.5
* Device Model: iPad 11th generation
* Is it jailbroken (name jailbreak used)? Nope
* How did you install UTM? Through a beta and stikdebug jit exploit

**Crash log**
If the app crashed, you need a crash log. To get your crash log, open the Settings app and browse to `Privacy -> Analytics & Improvements -> Analytics Data` and find the latest entry for UTM. You should export the text and attach it here.

**Debug log**
For all issues, _including_ crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the bottom of the configuration options (or at the top of the `QEMU` page) is `Debug Log`. Turn it on and save the VM. After you experience the issue, quit the VM and re-launch UTM. Open the VM settings again and select `Export Log...` and attach it here.

**Upload VM**
(Optional) If possible, upload the `config.plist` inside the `.utm`. If you do not have this, you can upload the entire `.utm` but note this contains your personal data. Since GitHub has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

Reproduce the distorted colors with Android 9 on UTM Beta v5.0.3, then enable Debug Log in the VM settings and export it after relaunching UTM. Inspect the exported log and, if needed, the VM's config.plist to identify the pixel-format mismatch; done means the Android display renders with correct colors.

Written by the indexing model from the issue text.