Run Android E2E with ARM64 APKs

[cortinico]

Summary:

Build only the arm64-v8a Android ABI for dry-run CI artifacts and run the ARM64 RNTester and template-app APKs on an API 35 google_apis x86_64 emulator using the system images built-in NDK translation support.

This also makes the Maestro emulator API level and target configurable, logs the device ABI/native-bridge configuration, and updates local RNTester artifact selection to use the ARM64 split.

Release and nightly publication builds continue to build all supported Android ABIs.

Changelog:

[INTERNAL] [CHANGED] - Run Android E2E tests with ARM64 APKs through NDK translation.

Test Plan:

• node --check .github/workflow-scripts/maestro-android.js — passed.
• node --check scripts/release-testing/test-release-local.js — passed.
• Parsed all modified YAML files with the yaml Node package — passed.
• ./node_modules/.bin/prettier --check <modified files> — passed.
• git diff --check HEAD~3..HEAD — passed.
• actionlint reported only existing repository metadata warnings for the custom 4-core-ubuntu label and the missing description in the local yarn-install action.
• yarn test .github/workflow-scripts/__tests__/maestro-android-test.js --runInBand could not start because the local dependency tree is missing flow-parser; restoring dependencies was blocked by HTTP 503 responses from the npm registry.
• The draft CI run should validate ARM64 APK installation, Hermes startup, and the complete Maestro suites through libndk_translation.so.

[meta-codesync]

@cortinico has imported this pull request. If you are a Meta employee, you can view this in D117195078.

[meta-codesync]

@cortinico merged this pull request in 25ebffd.