[expo] Send a warning for missing native modules

[Kudo]

Why

the native modules checking will throw an error that is too aggressive and the error stacktrace is little confused.

 ERROR  Error: Your JavaScript code tried to access a native module, FOO, that isn't supported in Expo Go.
To continue development with FOO, you need to create a development build of your app. See https://expo.fyi/missing-native-module for more info, 
including how to disable these errors.
 ERROR  Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
 ERROR  Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.

as we are not very confident with this approach in the meantime, we should send a warning rather than an error.

How

use console.warn than throwing errors.

Test Plan

• bare-expo + NativeModules.FOO in App.js

Checklist

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

[tsapeta]

Can we just remove this proxy? 😆 As I predicted, it brings more trouble than it's worth...

[Kudo]

Can we just remove this proxy? 😆 As I predicted, it brings more trouble than it's worth...

as the discussion, we will revert the native modules checking and reconsider it in sdk 48. i'll merge this pr to make sure we're doing right when we pick this feature back.