[NO QA]Manually update staging to use new GPG key in cherry pick workflow

[AndrewGable]

Details

Due to the way the deploy process works, we do not update the staging branch once the checklists are running, however we do update the GitHub workflow code on merge. This has caused a discrepancy in the workflow code and the GPG key on staging. This will update the key and code to match on staging, allowing us to test following these steps: https://github.com/Expensify/Expensify/issues/190171

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/190171#issuecomment-1003165197

Tests

1. Merge this PR
2. Verify the staging branch has the new GPG key
3. Cherry pick fix: room page layout #6951

QA Steps

N/A

[aldo-expensify]

GPG key has been updated in staging:

[aldo-expensify]

How do Cherry pick fix: room page layout #6951? Do you manually create a new PR from branch parasharrajat:room-page to stating?

[AndrewGable]

@aldo-expensify mobile deployers can run a manual cherry pick here: https://github.com/Expensify/App/actions/workflows/cherryPick.yml

I've kicked one off here!

[aldo-expensify]

Thanks!

[aldo-expensify]

It died, right? 😆

Update: oh no, it is fine I think: https://github.com/Expensify/App/pull/6964/files, do you want me to push a commit resolving the conflicts?

[AndrewGable]

It did die, but I forgot to delete the branch AndrewGable-cherry-pick-staging-6951 where it previously failed, so I deleted it. Then on re-run it worked! https://github.com/Expensify/App/actions/runs/1638813496

Yes, can you resolve the conflicts and merge the PR?

[OSBotify]

🚀 Cherry-picked to staging by @AndrewGable in version: 1.1.24-8 🚀

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

[OSBotify]

🚀 Deployed to production by @francoisl in version: 1.1.24-8 🚀

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