feat: add better server component support

[EvanBacon]

Summary:

• Move the top-level use client directive down to specific modules.
• This enables support for Platform.OS, StyleSheet.create, processColor, in react-server environments.
• Converted UnimplementedView to a function component since class components are not supported in RSC.
• Dimensions module has shims for StyleSheet/PixelRatio that are similar to react-native-web. We use typeof window === 'undefined' checks, which work on native since the react-native initial polyfill enforces that window is defined.

Changelog:

[ANDROID] [ADDED] - Added Platform.OS and StyleSheet.create support for react-server environments.
[IOS] [ADDED] - Added Platform.OS and StyleSheet.create support for react-server environments.

Test Plan:

• Ran this patch in an Expo SDK 52 project with server components enabled.

"use server";

import {
  Image,
  processColor,
  ScrollView,
  StyleSheet,
  Text,
  View,
  Modal,
  Platform,
  DrawerLayoutAndroid
} from "react-native";

export async function renderThing() {
  return (
    <View>
    <DrawerLayoutAndroid />
    <View style={styles.container}>
      <Text>Thing {JSON.stringify(processColor("blue"))} {Platform.OS}</Text>
      <Image source={require("@/assets/images/partial-react-logo.png")} />
      <ScrollView />
    </View>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    width: 100,
    height: 100,
    backgroundColor: "blue",
    borderWidth: StyleSheet.hairlineWidth,
  },
});

with execution:

<React.Suspense fallback={null}>{renderThing()}</React.Suspense>

[kassens]

Just regarding the Dimensions mock: I don't think other globals have mocks on the web either, right? Not a RSC expert, but returning random values doesn't seem great here as if those values are used on the server, it'll not match the client results.

[EvanBacon]

@kassens react-native-web / react-strict-dom are reasonable examples from the Meta team of server compatibility for client APIs. This mock was based on that behavior. Also worth noting that the hook equivalent will throw a React-themed error regarding dynamic behavior not being available in the server. The results will not match between server and client which is well known in the web community and results in hydration errors. There, you would use media queries and dynamic styles (100%, 3rem, etc).

Since we don't actually hydrate the views from an RSC payload before the JS loads, hydration isn't entirely relevant here.