[android, androidtv] `npx rnv run -p android -t non-existing IP:port` works differently on different OS

[GabrieleKaceviciute]

Describe the bug Both npx rnv run -p android -t non-paired-device-IP and -t non-existing-IP asks to pair device on macOS and Linux. On windows -> -t non-paired-device-IP asks to pair device. -t non-existing-IP -> asks to pick available target

To Reproduce

1. Go to template-starter package
2. Do npx rnv run -p android -t non-paired-device-IP -> asks to pair device (macos, linux, windows)
3. Do npx rnv run -p android -t non-existing-IP -> asks to pair device (macos, linux); asks to pick available target (windows)

Expected behavior -t non-existing-IP -> asks to pick available target on all OS

Desktop (please complete the following information):

• OS: macOS Ventura 13.6.4 M2
• Node Version 18.19.0
• RNV Version 1.0.0-rc.19

---

• OS: Windows 10 Pro
• Node Version 18.19.0
• RNV Version 1.0.0-rc.19

---

• OS: Ubuntu 20.04.5
• Node Version 18.20.2
• RNV Version 1.0.0-rc.19