DeployBlockerCash: Add labels, comment in slack, comment on issue

[roryabraham]

Details

Previously, when an Expensify.cash Deploy Blocker was created, we would just add the issue to the open StagingDeployCash checklist. This PR makes it so that we:

1. Add it to the StagingDeployCash checklist
2. Give it the Hourly and Demolition labels
3. Post the issue in Slack in the #deployer room
4. Comment on the issue with instructions that clarify the expectation for assignees.

Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/163893

QA Steps

0. Merge this PR
1. Label an issue DeployBlockerCash
2. Verify that the issue is given the Hourly and Demolition labels
3. Verify that someone from the Engineering Demolition team is auto-assigned to the issue.
4. Verify that the issue is posted in the #deployer slack room
5. Verify that OSBotify comments in the issue with a comment that looks like this:

Tested On

Can be live-tested on GitHub only (although I did test the issue comment in another repo I use for testing GH Actions).

[roryabraham]

@deetergp Since Andrew is OoO I'm requesting your review since I know you have some familiarity with the GH Actions YAML syntax.

[deetergp]

Looks good to me!

[roryabraham]

@Gonals In the spirit of #Urgency I'm going to go ahead and self-merge this so that any deploy blockers created today get auto-assigned with a high degree of urgency.

[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.

[OSBotify]

🚀 Deployed to staging in version: 1.0.46-1🚀

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

[isagoico]

@roryabraham Heyo!
Added the deploy blocker to this issue that was found around the IOU transactions. Seems like this PR is a fail but wanted to verify with you first #2969

[roryabraham]

Hi @isagoico . That PR was indeed a fail. I have a (hopefully) better one here.