Make the view manager prop setter caches thread-safe (#59245)

Summary:
`ViewManagersPropertyCache.CLASS_PROPS_CACHE` and the two setter maps in `ViewManagerPropertyUpdater` are static `HashMap`s. Two threads write them:

- the UI thread, when it updates the props of a view (`ViewManagerPropertyUpdater.updateProps` → `findManagerSetter`);
- the JS thread, when it builds a view config (`getConstantsForViewManager` → `ViewManager.nativeProps`).

In bridgeless mode, JS gets the view config of a lazy view manager on first use, during render. At that time, the UI thread can mount other views. Concurrent writes to a `HashMap` can lose entries or break the map.

This change uses `ConcurrentHashMap` for the three maps. The get-then-put code does not change. If two threads compute the same entry, the values are equal, so the second write is harmless. I did not use `computeIfAbsent`, because `getNativePropSettersForViewManagerClass` calls itself for the superclass.

This came up in the review of #59173, which sends the eager view managers through the same on-demand path.

## Changelog:

[ANDROID] [FIXED] - Make the view manager prop setter caches thread-safe

Pull Request resolved: #59245

Test Plan:
Unit tests: `./gradlew :packages:react-native:ReactAndroid:testDebugUnitTest --tests "com.facebook.react.uimanager.*"` passes (230 tests, 0 failures).

Device: Xiaomi Mi Note 2 (Snapdragon 821, Android 8.0). App: a production Expo app, release build, React Native 0.88.0, Hermes. I compiled this change and #59173 against 0.88.0 and replaced the same classes in `react-android-0.88.0-release.aar`. I measured from process start to the first frame with rows in the first list, 12 cold starts for each build.

| Build | Median | Range | `getConstants()` |
|---|---|---|---|
| Stock 0.88.0 | 2416 ms | 2335–2477 ms | 215 ms (45 keys) |
| #59173 + this change | 2243 ms | 2187–2406 ms | 45 ms (5 keys) |

To see the cost of this change alone, I also used a build whose JS does not call `getConstants()` at startup, so the first view configs come from `getConstantsForViewManager()` during render. Without this change: 2189 ms median (2140–2236 ms). With it: 2192 ms median (2156–2244 ms). I see no difference.

Same chat app with threads list and messages. With this change, I opened the chat list, a thread, settings, the theme list, the profile and the contacts, and scrolled. Logcat shows no crash and no view config errors.

Reviewed By: christophpurrer

Differential Revision: D126631569

Pulled By: javache

fbshipit-source-id: ae455c2a152f9dcf6e5bec172005db9e654e7193

Author: brownrice777

packages/react-native/ReactAndroid/src/main/java/com/facebook/react/uimanager/ViewManagerPropertyUpdater.kt

@@ -12,6 +12,7 @@ import com.facebook.common.logging.FLog
 import com.facebook.react.bridge.ReadableArray
 import com.facebook.react.uimanager.ViewManagersPropertyCache.PropSetter
 import java.util.HashMap
+import java.util.concurrent.ConcurrentHashMap
 
 @Suppress("DEPRECATION")
 public object ViewManagerPropertyUpdater {
@@ -31,8 +32,11 @@ public object ViewManagerPropertyUpdater {
 
   private const val TAG = "ViewManagerPropertyUpdater"
 
-  private val VIEW_MANAGER_SETTER_MAP: MutableMap<Class<*>, ViewManagerSetter<*, *>> = HashMap()
-  private val SHADOW_NODE_SETTER_MAP: MutableMap<Class<*>, ShadowNodeSetter<*>> = HashMap()
+  // Used from the JS thread (view configs) and the UI thread (prop updates).
+  private val VIEW_MANAGER_SETTER_MAP: MutableMap<Class<*>, ViewManagerSetter<*, *>> =
+      ConcurrentHashMap()
+  private val SHADOW_NODE_SETTER_MAP: MutableMap<Class<*>, ShadowNodeSetter<*>> =
+      ConcurrentHashMap()
 
   @JvmStatic
   public fun clear() {

packages/react-native/ReactAndroid/src/main/java/com/facebook/react/uimanager/ViewManagersPropertyCache.kt

@@ -21,6 +21,7 @@ import com.facebook.react.uimanager.annotations.ReactProp
 import com.facebook.react.uimanager.annotations.ReactPropGroup
 import com.facebook.yoga.YogaValue
 import java.lang.reflect.Method
+import java.util.concurrent.ConcurrentHashMap
 
 /**
  * This class is responsible for holding view manager property setters and is used in a process of
@@ -29,7 +30,8 @@ import java.lang.reflect.Method
 @Suppress("DEPRECATION") // ReactShadowNode is @Deprecated but still required by this cache.
 internal object ViewManagersPropertyCache {
 
-  private val CLASS_PROPS_CACHE: MutableMap<Class<*>, Map<String, PropSetter>> = HashMap()
+  // Used from the JS thread (view configs) and the UI thread (prop updates).
+  private val CLASS_PROPS_CACHE: MutableMap<Class<*>, Map<String, PropSetter>> = ConcurrentHashMap()
   private val EMPTY_PROPS_MAP: MutableMap<String, PropSetter> = HashMap()
 
   @JvmStatic