[menu-bar][cli] Add basic support for launching Expo updates

[gabrieldonadel]

Why

Expo Updates are a big part of EAS and Orbit should be able to directly launch them into devices and simulators.

Closes ENG-11072
Closes #113

How

• Add new launch-update command
• Add @expo/multipart-body-parser and expo-manifests dependencies
• Add Emulator.getRunningDeviceAsync and Simulator.isSimulatorAsync helper functions
• Refactor deeplink parsing on menu-bar

Officially supported formats

This PR adds basic support for launching Expo updates that use the following formats:

• expo-orbit//update/u.expo.dev/:appId/channel/:channelId?platform=(android|ios)
• expo-orbit//update/u.expo.dev/:appId/branch/:branchId?platform=(android|ios)
• expo-orbit//update/u.expo.dev/:appId/group/:groupId?platform=(android|ios)
• expo-orbit//update/u.expo.dev/:appId/update/:updateId?platform=(android|ios)

Note

As long as the URL specifies the “platform” in the query params Orbit should be able to launch any update.

Test Plan

Scenario 1 (An app that uses dev-client)

1. Create development builds on EAS for Android and iOS
2. Create a new update
3. Launch Orbit using the update URL
   3.1. Most recent development build for that runtime version should be installed automatically
   3.2. Update should be launched

Scenario 2 (An app that does not use dev-client)

1. Create a new update (runtimeVersion=exposdk:X.X.X)
2. Launch Orbit using the update URL
   2.1. Expo Go for that sdk should be installed automatically
   2.2. Update should be launched

[linear]

ENG-11072 Add support for launching expo-updates with Orbit

[alanjhughes]

LGTM. Left a few nits but totally up to you if you want to do anything about them or not