Fix concurrent consumers issue with ReactMarker (#38710)

Summary:
Pull Request resolved: #38710

Fix a race condition when multiple consumers try to access ReactMarker and trigger calls to native module. Even though ReactMarker uses `ConcurrentLinkedQueue`, the loop itself could race and cause NPE.

Changelog:
[Android][Fixed] - Fix race condition with ReactMarker calls to its native module

Reviewed By: rshest

Differential Revision: D47933993

fbshipit-source-id: 502fa95b69aae07444bf48a5f30c094750abed25

packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/ReactMarker.java

@@ -193,8 +193,8 @@ private static void notifyNativeMarker(ReactMarkerConstants name, @Nullable Long
       nativeLogMarker(name.name(), now);
 
       // Then send all cached native ReactMarkers
-      while (!sNativeReactMarkerQueue.isEmpty()) {
-        ReactMarkerRecord record = sNativeReactMarkerQueue.poll();
+      ReactMarkerRecord record;
+      while ((record = sNativeReactMarkerQueue.poll()) != null) {
         nativeLogMarker(record.getMarkerName(), record.getMarkerTime());
       }
     } else {