feat(git-node): add support for promoting several releases at once

[aduh95]

And from a different remote. Currently, the git node release --promote workflow doesn't work well for security releases as it assumes the release proposal exists on the same repo as where we want to make the release, and releases are to be released one-by-one.
This PR aims at addressing all this shortcomings.

The process is now roughly:

1. for each proposal PR:
   1. Verify if it's ready (correct date, changelog entry, etc.).
   2. Create a signed tag for it.
   3. create a Working on … commit.
   4. rebase the public staging branch.
2. checkout the default branch, and cherry-pick all releases commit on top of it.
3. Print out a single git push command to push everything at once to the public repo.
4. Rest of the workflow is not affected.

I've tested this with 24.1.0 and 22.16.0, seems to work fine!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.76%. Comparing base (197134f) to head (b19f363).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #935   +/-   ##
=======================================
  Coverage   79.76%   79.76%           
=======================================
  Files          39       39           
  Lines        4630     4630           
=======================================
  Hits         3693     3693           
  Misses        937      937           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.