Publishing pipeline fixes

[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

After #1914, we had several issues with our publishing script.

• beachball unexpectedly tried to bump and publish react-native-macos from the main branch.
• The canary publish failed because we moved the core bits of react-native-macos to a new location.

While we don't have a full fix for the first issue yet, we can at least finish the job and bump all the relevant version numbers as needed.

The second issue gets resolved by 847315f.

Changelog

[INTERNAL] [FIXED] - Fix publishing pipeline issues

Test Plan

As long as our publishing pipeline holds up, we should be good.