[expo] Send a warning for missing native modules (#19845)

# Why

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

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

packages/expo/CHANGELOG.md

@@ -8,6 +8,8 @@
 
 ### 🐛 Bug fixes
 
+- Showing warnings for missing native modules rather than throwing errors. ([#19845](https://github.com/expo/expo/pull/19845) by [@kudo](https://github.com/kudo))
+
 ### 💡 Others
 
 ## 47.0.0-beta.8 — 2022-11-02

packages/expo/src/proxies/NativeModules.ts

@@ -79,9 +79,9 @@ export function createProxyForNativeModules(NativeModules: any) {
           target.NativeUnimoduleProxy?.modulesConstants.ExponentConstants?.executionEnvironment ===
             ExecutionEnvironment.StoreClient;
         if (isRunningInStoreClient) {
-          throw new Error(createErrorMessageForStoreClient(prop));
+          console.warn(createErrorMessageForStoreClient(prop));
         } else if (target.EXDevLauncher) {
-          throw new Error(createErrorMessageForDevelopmentBuild(prop));
+          console.warn(createErrorMessageForDevelopmentBuild(prop));
         }
       }
       return value;