[Android] Internal Android arm32 and arm64 device CI runs are failing

Both arm32 and arm64 CI jobs are being directed to the ubuntu android.29 queue which is an emulator queue. Xharness reports that the respective arm32 and arm64 devices are not found.

Since we don't have internal device queue, we should explore the possibility of running these in emulation mode. Based on a quick search, we might need an API 30+ to run these as such android.29 queue might not be compatible.

cc: @vitek-karas

Start by tracing the arm32 and arm64 Android CI job configuration that directs both runs to the ubuntu android.29 queue, then review the XHarness missing-device reports. Verify whether API 30+ emulation supports these runs and consider the work complete when both jobs execute successfully without reporting missing arm32 or arm64 devices.

Written by the indexing model from the issue text.