Do not log warning for missing feature flags native module in tests (#51629)

Summary:
Pull Request resolved: #51629

Changelog: [internal]

The native module will never be defined in tests, so there's no point in logging this warning there.

Reviewed By: rshest

Differential Revision: D75451414

fbshipit-source-id: cdc1f674d01fcaf58c1c2342c994d95e6b3b6847

Author: rubennorte

packages/react-native/src/private/featureflags/ReactNativeFeatureFlagsBase.js

@@ -102,6 +102,8 @@ const hasTurboModules =
 function maybeLogUnavailableNativeModuleError(configName: string): void {
   if (
     !NativeReactNativeFeatureFlags &&
+    // Don't log in tests.
+    process.env.NODE_ENV !== 'test' &&
     // Don't log more than once per config
     !reportedConfigNames.has(configName) &&
     // Don't log in the legacy architecture.

packages/react-native/src/private/featureflags/__tests__/ReactNativeFeatureFlags-test.js

@@ -8,6 +8,10 @@
  * @format
  */
 
+// Pretend to not run in a testing environment so we log the warning for the
+// missing native module to the console.
+process.env.NODE_ENV = 'development';
+
 describe('ReactNativeFeatureFlags', () => {
   beforeEach(() => {
     jest.unmock('../specs/NativeReactNativeFeatureFlags');