Change null-check in DefaultComponentsRegistry (#42731)

Summary:
Pull Request resolved: #42731

This matches the behaviour we have for DefaultTurboModuleManagerDelegate, where we handle the lack of this being set gracefully. It's probably worth still logging this, as it may point at an incorrectly configured app.

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D53048064

fbshipit-source-id: 3ef10da3a7779a1274a1a1793387cf8cdf36c535

Author: javache

packages/react-native/ReactAndroid/src/main/jni/react/newarchdefaults/DefaultComponentsRegistry.cpp

@@ -25,12 +25,13 @@ std::shared_ptr<const ComponentDescriptorProviderRegistry>
 DefaultComponentsRegistry::sharedProviderRegistry() {
   auto providerRegistry = CoreComponentsRegistry::sharedProviderRegistry();
 
-  react_native_assert(
-      DefaultComponentsRegistry::registerComponentDescriptorsFromEntryPoint &&
-      "'registerComponentDescriptorsFromEntryPoint' was not initialized in 'JNI_OnLoad'");
-
-  (DefaultComponentsRegistry::registerComponentDescriptorsFromEntryPoint)(
-      providerRegistry);
+  if (DefaultComponentsRegistry::registerComponentDescriptorsFromEntryPoint) {
+    (DefaultComponentsRegistry::registerComponentDescriptorsFromEntryPoint)(
+        providerRegistry);
+  } else {
+    LOG(WARNING)
+        << "Custom component descriptors were not configured from JNI_OnLoad";
+  }
 
   return providerRegistry;
 }