Fix dex2oat wrapper SELinux check on Android 14+

[pbzin]

Summary

• detect the Android 14+ artd to dex2oat_exec transition when selecting the wrapper file context
• keep the existing dex2oat execute_no_trans check for Android versions before 14

Root cause

Android 14 introduced the artd service path for dex2oat. The previous check queried dex2oat with execute_no_trans; on Android 16 this check fails because the supported path is the artd -> dex2oat_exec -> dex2oat domain transition. Vector therefore selected the xposed_file fallback for its bind-mounted wrapper. artd then failed to execute the wrapper because the module policy only grants xposed_file access to the older domains.

The fix uses the platform transition already defined by AOSP, so it does not broaden the module policy with an artd access rule for xposed_file.

Validation

• Reproduced on a Redmi Note 13 4G running an Android 16 user build: the old path mounted dex2oat64 with xposed_file, and artd logged Permission denied.
• Confirmed the installed AOSP Android 16 policy defines domain_auto_trans(artd, dex2oat_exec, dex2oat).
• git diff --check passes.
• No full build was run.

[JingMatrix]

@pbzin Please upload your logs in Redmi Note 13 4G for me to better understand what you described.