[0.87] Fix skipped post-publish jobs in release mode

[cipolleschi]

Summary

Backport of #57479 to 0.87-stable.

During the 0.87.0-rc.0 release, the npm packages published successfully (publish_react_native ✓) but every release-only downstream job was skipped: post_publish, generate_changelog, bump_podfile_lock, and create_draft_release. As a result the community template was not published, rn-diff-purge was not triggered, npm/Maven verification did not run, the changelog was not generated, Podfile.lock was not bumped, and no draft GitHub release was created.

Root cause

These four jobs gate on a bare condition:

if: needs.determine_mode.outputs.mode == 'release'

Because that expression contains no status-check function, GitHub Actions implicitly ANDs a success() gate, which evaluates to false when there is a skipped job in the dependency graph. In release mode, build_android (a dependency of publish_react_native) is always skipped, poisoning the implicit success() for these downstream jobs — so they skip even after a fully successful publish.

publish_react_native already works around exactly this with always() + explicit .result == 'success' checks. This PR applies the same pattern to the four downstream jobs.

Fix

if: |
  always() &&
  needs.determine_mode.result == 'success' &&
  needs.publish_react_native.result == 'success' &&
  needs.determine_mode.outputs.mode == 'release'

(create_draft_release checks generate_changelog and set_hermes_version instead, matching its needs.)

Test plan

• YAML validated locally.
• Verify on the next 0.87 release that the four downstream jobs run after publish_react_native succeeds.

[github-actions]

Caution

Missing Changelog

Please add a Changelog to your PR description. See Changelog format