In #170536, we wanted to publish an older 3.32 as 3.32.4:

https://flutter-dashboard.appspot.com/#/build?repo=flutter&branch=flutter-3.32-candidate.0

... I.e. 8defaa7, originally 3.32.2, effectively reverting 3.32.3.

Unfortunately, there is no way to do that today - the release tooling only accepts a candidate branch (such as flutter-3.32-candidate.0) and a release channel (such as stable), meaning that there is no way to say "publish existing pre-built artifacts X as release Y" unless X is the latest commit in a candidate branch.

Scope of work required to do this:

• Update release_publish.py so that rel_hash can be user-defined (as an input)
• Update the internal tool proxy to allow that variable and pass it in if used
• Update the release playbook to explain this as a workaround

I don't believe we need to update push_release.sh, the existing REL_HASH variable should be usable.

Here is an example invocation of the release_publish recipe:

{
  "clobber": false,
  "device_type": "none",
  "force": false,
  "git_branch": "flutter-3.32-candidate.0",
  "goma_jobs": "0",
  "no_goma": true,
  "recipe": "release/release_publish",
  "release_channel": "stable",
  "tag": "3.32.3"
}