Mark 0.72 as ready for release

[amgleitman]

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

Right now, our publishing pipeline doesn't elegantly handle the case of promoting from a prerelease to a proper release. We fix this by adding a special prerelease name, ready, that indicates that we're ready to release.

We opt for this instead of just going to 0.72.0 directly because our publishing pipeline will bump again to 0.72.1, which isn't ideal. While it would be nice to get beachball up and running so we don't have to worry about this stuff manually, it would undoubtedly be more expensive to get beachball up and running, so this should be a satisfactory workaround for now.

Changelog

[INTERNAL] [FIXED] - More pipeline fixes

Test Plan

We'll have to test this against our actual publishing pipeline.