fix(platform-android): avoid probing physical devices as emulators

[kateinoigakukun]

Description

When we specify an android emulator as the harness runner like below and connect a physical device, we get the following error.

const config = {
  runners: [
    androidPlatform({
      name: 'android',
      device: androidEmulator('Pixel_Tablet_Rootable'),
      bundleId: 'com.example',
    }),
  ]
};

export default config;

SubprocessError: Command failed with exit code 1: ~/Library/Android/sdk/platform-tools/adb -s <device-id> emu avd name
    at checkFailure (file:///path/to/node_modules/nano-spawn/source/result.js:40:9)
    at getResult (file:///path/to/node_modules/nano-spawn/source/result.js:17:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async Module.getEmulatorName (file:///path/to/node_modules/@react-native-harness/platform-android/dist/adb.js:195:24)
    at async getAdbId (file:///path/to/node_modules/@react-native-harness/platform-android/dist/adb-id.js:10:34)
    at async getAndroidEmulatorPlatformInstance (file:///path/to/node_modules/@react-native-harness/platform-android/dist/instance.js:108:17)
    at async Object.work (file:///path/to/node_modules/@react-native-harness/jest/dist/harness.js:217:36)
    at async withPlatformReadyTimeout (file:///path/to/node_modules/@react-native-harness/jest/dist/harness.js:36:16)
    at async Promise.all (index 1)
    at async file:///path/to/node_modules/@react-native-harness/jest/dist/harness.js:202:24

This is just because getAdbId tries to get an emulator name from a physical device.
This patch fixes Android emulator device resolution to skip non-emulator ADB IDs before querying AVD name. Also adds a focused regression test suite.

Testing

I manually tested with that previously problematic situation.

[vercel]

@kateinoigakukun is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.