mark all of react-native as client boundary for React Server Components

[EvanBacon]

Summary:

While developing React Server Component support for React Native, I've been adding this patch to the react-native package. It opts the entire react-native package out of being server rendered.

In the future, we'll want to circle back and refactor the react-native package to be more isomorphic so we can allow for utilities like processColor to be used in server bundles that target native platforms.

Changelog:

[GENERAL] [ADDED] - Added support for importing react-native in a react-server environment for React Server Components support.

Test Plan:

Using react-native with this patch in a framework that supports React Server Components for native platforms, such as my unreleased branch of Expo Router, will allow for server rendering views from react-native to RSC Flight code with client references to the react-native package, e.g.

import { View } from 'react-native';

export default function App() {
  return <View testID="basic-view" style={{ "backgroundColor":"#191A20" }}/>
}

Can be server rendered to ↓

2:I["/node_modules/react-native/index.bundle?platform=ios&dev=true#798513620",["..."],"View"]
1:["$","$L2",null,{"testID":"basic-view","style":{"backgroundColor":"#191A20"}}]

The client boundaries (URL paths) are specific to the current Expo CLI implementation (based on Metro) and may look different in other implementations.

[facebook-github-bot]

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