Update StagingDeployCash for manual cherry-picks

[roryabraham]

Details

If the cherryPick.yml workflow was run manually (i.e: by a user other than OSBotify), then we need to update the deploy checklist to include the newly deployed PR.

Fixed Issues

$ #4379

Tests

1. Merge this PR with the deploy checklist locked.
2. Manually CP this PR.
3. Verify that, once the CP workflow completes, the checklist is updated to include this PR.

QA Steps

None.

[nkuoch]

Thanks! Adding @tgolen as a final reviewer as he's more familiar with the process.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[roryabraham]

Manually CPing this to test if it works!

[roryabraham]

JK, it's already been added to the checklist. So I'll have to remember to test this with another PR.

[roryabraham]

This did not work as expected. I forgot that the createOrUpdateStagingDeploy action relies on the new tag having been created in the runner. Will create a follow-up PR to fix.

[roryabraham]

This failure was fortuitous, as it maybe led me to a revelation of how to fix a related bug that has been marring me for months now. In case you're curious....

But that means that the fix for this is maybe actually a bit greater in scope than a quick follow-up, so we should revert this. It's not actually breaking anything, just causing red herring CP workflow failures.

[roryabraham]

Revert PR is ready: #4815

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅