[expo][expo-dev-launcher] improve error messaging in development clients

[esamelson]

Why

resolves ENG-5315

Adds some messaging to Expo Go to direct developers to custom development builds (dev clients) if they try to access a native module that doesn't exist.

This PR essentially ports our existing implementation from expo-dev-launcher into the expo package, for use in Expo Go. This does not catch all cases where a missing native module is accessed, but is a fairly straightforward change that will catch at least some cases (most specifically, those modules that try to create a NativeEventEmitter on iOS) while we work on a broader solution.

How

If in Expo Go, replace the global JS error handler with one that does the following:

• replaces the Native module cannot be null message and its newer counterpart with a more helpful message directing users to dev clients
• appends a similar message to CodedErrors with the code ERR_UNAVAILABLE (errors stemming from missing expo modules)
• suppresses the unhelpful Application "main" has not been registered error, if another error was logged beforehand.

Additionally, I updated the dev-launcher's implementation to look for the new counterpart of the Native module cannot be null message, which was changed in RN 0.65.

Test Plan

I am not sure which external modules can be used to test this -- I tried react-native-ble-manager, but it does not use a NativeEventEmitter, and so it doesn't trigger our code. However, I triggered it manually by calling new NativeEventEmitter(null) to ensure the error is intercepted correctly:

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• This diff will work correctly for expo build (eg: updated @expo/xdl).
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-5315 Catch errors from missing native module in Expo Go

and direct users to dev client