[No QA] Create callable worklow for createNewVersion

[roryabraham]

Details

This change is part of a larger undertaking to clean up our GitHub Actions to make them faster, simpler, and more approachable.

Fixed Issues

$ (partial) https://github.com/Expensify/Expensify/issues/195693

Tests

1. Merge PR A with the checklist unlocked.
2. A staging deploy should occur and when it completes PR A should get a deploy comment and should be added to the checklist.
3. Merge PR B with the checklist locked.
4. PR B should get a comment saying it's not being immediately deployed.
5. Merge PR C with the checklist locked and with a CP Staging label.
6. PR C should be CP'd to staging. It should be added to the checklist and when the deploy completes it should get a deploy comment.
7. Close the checklist.
8. A production deploy should occur, and PRs A and C should receive a deploy comment.
9. PR B should be deployed to staging and receive a deploy comment.

[roryabraham]

We also might be able to simplify this callable workflow by using secrets: inherit:

If the secrets are inherited using secrets: inherit, you can reference them even if they are not defined in the on key.

This sounds convenient, we just have to decide if it's safe practice. I actually think it will be safe for any callable workflow that we own and which comes from the same repo

[roryabraham]

Created an issue for the last actionlint failure: rhysd/actionlint#174

[AndrewGable]

Looks good! 👍

[roryabraham]

https://github.com/Expensify/App/actions/runs/2659622994

[OSBotify]

🚀 Deployed to production by @chiragsalian in version: 1.1.84-13 🚀

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