[dev-launcher][dev-menu][ios] Add support for Fabric (#22184)

# Why

Closes ENG-7955

This PR adds dev-launcher support for the new architecture.

# How

- Updates `expo-dev-launcher` an

[dev-launcher][dev-menu][ios] Add support for Fabric (#22184)

# Why

Closes ENG-7955

This PR adds dev-launcher support for the new architecture.

# How

- Updates `expo-dev-launcher` and `expo-dev-menu` podspecs to support
`NEW_ARCH_ENABLED` flags
- Add `EXDevLauncherBridgeDelegate` class that inherits from
`RCTAppDelegate` and is responsible for creating the root view and
bridge
- Replace `DevMenuRCTCxxBridgeDelegate`with `DevMenuRCTAppDelegate`
- Fix `EXDevLauncherBridgeDelegate` not able to relaunch DevLauncher
- Add `ExpoDevLauncherBridgeDelegateHandler` to handle opening apps from
`ExpoDevLauncherReactDelegateHandler`
- Update `openDevMenuFromReactNative` to ensure the DevMenu is closed
before opening the react-native dev menu


# Test Plan

Run `fabric-tester` and `bare-expo` on iOS


<table>
<tr><th>fabric-tester</th><th>bare-expo</th></tr>
<tr>
<td>
<video
src="https://github.com/expo/expo/assets/11707729/1176f862-4459-4a39-8c11-16f73b2dfe46"/>
</td>
<td>
<video
src="https://github.com/expo/expo/assets/11707729/5f603af5-d970-4144-ade6-0943b829d225"
/>
</td>
</tr>
</table>

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

---------

Co-authored-by: Kudo Chien <[email protected]>

show more ...

[menu][iOS] Migrate to new modules API (#22263)

# Why

In order to add support for Fabric to expo-dev-client and related
libraries we must migrate all related modules to the new API

Related to

[menu][iOS] Migrate to new modules API (#22263)

# Why

In order to add support for Fabric to expo-dev-client and related
libraries we must migrate all related modules to the new API

Related to ENG-7955


# How

Migrate ExpoDevMenu classes to use the new modules API

# Test Plan

Run dev client through bare expo

<table>
<tr>
<td>
<img
src="https://user-images.githubusercontent.com/11707729/234351876-9402cba1-686a-4575-b2e7-6319e9c50439.png"
/>
</td>
<td>
<img
src="https://user-images.githubusercontent.com/11707729/234351912-f60b5e59-f9b5-4358-9402-ac5e91794bb7.png"
/>
</td>
</tr>
</table>


# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

show more ...