Implement multiple view manager lookup for the interop layer on Android

[gabrieldonadel]

Summary:

When running with the new architurece and using the renderer interop layer on Android, view managers don't work if their names start with RCT. This happens because the RCT prefix is automatically removed from the component name, and inside the internal mViewManagers we store view managers with the RCT prefix.

Using the RCT pattern as a prefix works fine with the old architecture and is actually used on the Android Native UI Components tutorial in the docs, making me believe that this same patterns is used across many community libraries.

This diff adds a secondary lookup logic for view managers:

1. We look for the XXXViewManager.
2. If not found, we look for RCTXXXViewManager.

Quite similar to the iOS implementation introduced in #38093

---

With this change we can also remove most of the entries from FabricNameComponentMapping (I can address this in a follow up PR)

react-native/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/fabric/mounting/mountitems/FabricNameComponentMapping.java

Lines 22 to 45 in 4e6eba7

	class FabricNameComponentMapping {
	private static @NonNull final Map<String, String> sComponentNames = new HashMap<>();
	static {
	// TODO T97384889: unify component names between JS - Android - iOS - C++
	sComponentNames.put("View", "RCTView");
	sComponentNames.put("Image", "RCTImageView");
	sComponentNames.put("ScrollView", "RCTScrollView");
	sComponentNames.put("Slider", "RCTSlider");
	sComponentNames.put("ModalHostView", "RCTModalHostView");
	sComponentNames.put("Paragraph", "RCTText");
	sComponentNames.put("Text", "RCText");
	sComponentNames.put("RawText", "RCTRawText");
	sComponentNames.put("ActivityIndicatorView", "AndroidProgressBar");
	sComponentNames.put("ShimmeringView", "RKShimmeringView");
	sComponentNames.put("TemplateView", "RCTTemplateView");
	sComponentNames.put("AxialGradientView", "RCTAxialGradientView");
	sComponentNames.put("Video", "RCTVideo");
	sComponentNames.put("Map", "RCTMap");
	sComponentNames.put("WebView", "RCTWebView");
	sComponentNames.put("Keyframes", "RCTKeyframes");
	sComponentNames.put("ImpressionTrackingView", "RCTImpressionTrackingView");
	}

Changelog:

[ANDROID] [ADDED] - Implement multiple view manager lookup for the interop layer

Test Plan:

Tested installing a library such as react-native-fbsdk-next that names its view managers starting with RCT

Before	After

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	18,093,685	+1
android	hermes	armeabi-v7a	n/a	--
android	hermes	x86	n/a	--
android	hermes	x86_64	n/a	--
android	jsc	arm64-v8a	21,462,802	+7
android	jsc	armeabi-v7a	n/a	--
android	jsc	x86	n/a	--
android	jsc	x86_64	n/a	--

Base commit: c574ca5
Branch: main

[brentvatne]

this seems very reasonable to me! it's consistent with the ios behavior, and it should help make it easier for folks to adopt the new arch. i'd love to see this land in 0.74

[facebook-github-bot]

@arushikesarwani94 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@arushikesarwani94 merged this pull request in 15a5638.

[cortinico]

@gabrieldonadel can you add a pick request on https://github.com/reactwg/react-native-releases/issues/new/choose for this one?

[gabrieldonadel]

@gabrieldonadel can you add a pick request on https://github.com/reactwg/react-native-releases/issues/new/choose for this one?

Yep, already did it yesterday reactwg/react-native-releases#172. Thanks for the remainder