[No QA] Add deployer GH handle to deploy messages

[roryabraham]

@AndrewGable Will you please review this?

Details

This adds the deployer's GH handle to deploy messages, where the deployer is defined as:

1. For production deploys, the person who closed the checklist to trigger the deploy.
2. For normal staging deploys, the person who merged the PR.
3. For "automatic" CPs (using the CP Staging label), the person who merged the PR.
4. For manual CPs using the GH UI, the person who triggered the workflow. (We are going to save this by including the actor's GH handle in the CP branch name.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/168264

Tests

1. Ensure that the deploy checklist is unlocked.
2. Merge this PR, and after the staging deploy completes, verify that it gets a "Deployed to staging by <whoever merged it>" comment.
3. Lock the deploy checklist.
4. Create and merge another PR with the CP Staging label. Verify that it gets a "Cherry-picked to staging by <whoever merged it>" comment.
5. Manually CP a PR using the GH UI. For testing purposes, the person who manually CPs the PR should be different than the person who merged it. After the staging deploy completes. verify that it gets a "Cherry-picked to staging by <whoever manually triggered the CP>" comment.

QA Steps

None.

Tested On

n/a, GH only. But I did do a lot of incremental testing using a local octokit instance while developing.

[luacmartins]

Code LGTM! Couldn't test locally, so I'm interested to see how that goes.

[AndrewGable]

Is there no way to get this or pass this along a different way?

[AndrewGable]

Maybe via the API to check for a workflow https://docs.github.com/en/rest/reference/actions#list-workflow-runs ?

[roryabraham]

I agree this feels hacky, but the difficult part with using this API is identifying the workflow run that's associated with a given PR or version. Let me dig into it a bit.

[roryabraham]

Basically, the information we have when we're running markPullRequestsAsDeployed is:

1. The version
2. The PR number

Then given those, we would need to find the cherryPick.yml workflow run that:

1. Generated that version, OR
2. Was executed with that PR number as input.

But unfortunately the inputs to a workflow run are not saved by their API, so I wasn't able to see how we could identify the correct workflow run.

[roryabraham]

Open to suggestions if you see something I'm missing

[AndrewGable]

I don't see anything on the API docs on first read, but let me keep looking a bit further.

[AndrewGable]

Looks great- Feel free to merge when you are ready to test @roryabraham

[roryabraham]

Looks like we missed the chance to test this while the current checklist was still unlocked 😞 Gotta test it during the next deploy cycle. @isagoico can you ping or DM me before adding the lock label to the next checklist? Thanks!

[roryabraham]

Testing this out now

[roryabraham]

Unfortunately it looks like this didn't work as expected https://github.com/Expensify/App/runs/3303693182?check_suite_focus=true

[roryabraham]

We've got one successful test for a PR merged w/ the CP Staging label: #4568 (comment)

[OSBotify]

🚀 Deployed to staging by @roryabraham in version: 1.0.83-5 🚀

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

[roryabraham]

Okay, just verified over here that this is fully functional now

[OSBotify]

🚀 Deployed to production by @isagoico in version: 1.0.85-9 🚀

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