ci: add a pipeline for consuming react-native-macos

[Tommy Nguyen (tido64)]

Please select one of the following

• I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
• I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
• I am making a fix / change for the macOS implementation of react-native
• I am making a change required for Microsoft usage of react-native

Summary

Add a pipeline for consuming react-native-macos outside of the repository. This should help catch issues earlier (such as #860 or FBReactNativeSpec not being generated).

Changelog

[Internal] [Added] - Add a pipeline for consuming react-native-macos outside the repository

Test Plan

The newline pipeline should install and build react-native-macos. It will fail because FBReactNativeSpec.h/.mm are not being generated.

[Andrew Coates (acoates-ms)]

Could not find /.ado/apple-node-setup.yml

[Tommy Nguyen (tido64)]

It looks like the latest failure on the Integration pipeline is from having both @react-native-community/cli 4.x and 5.x installed. We get auto-linking from 5.x but use config from 4.x, and some of the paths are wrong. At some point, the main branch will get caught up with the latest changes and start using 5.x so this will be resolved eventually. Do you think it makes sense to make sure we always use 5.x, or should we wait till we are caught up?

Edit: Never mind. We can pull the version from package.json. The pipeline now fails because of codegen, which is expected since main hasn't caught up yet.