Fix publish.yml

[Saadnajmi]

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

publish.yml wasn't quite good in our last PR. Let's make some updates. Namely, let's fix all the steps that are conditional on branch names to use the right branch name (refs/head/main instead of just main).

The Intent is that on main we publish releases of type nightly (AKA, a rollling release of the latest bits), and on *-stable branches, we publish releases (I.E: 0.68.4, 0.71.0, etc...). The flow of what node scripts to call is slightly different between nightly and release, and I try to control that via conditions on each Azure Pipeline step. Namely, release jobs need an extra call to prepare-package-for-release.js.

Note: nightly is not entirely accurate, since we publish every commit (a canary), not every night. In practice, I don't think the label should matter.

Changelog

[INTERNAL] [FIXED] - Fix publish.yml

Test Plan

I copied the publish job to apple-pr.yml and tested as much as I could. Unfortunately, it's not a perfect test, as I had to fudge some environment variables.

[harrieshin]

is it just really branch name changes? it does seem like nightly release now?

[Saadnajmi]

This again merged while I still had a change I caught in PR that I wanted to fix... can we please disable automatic automerges?