Update staging to 1.0.16-0

[roryabraham]

Details

For a while now, the Github Workflow that's supposed to update the staging branch has been silently failing (example). We haven't noticed because for the time being we've been deploying staging from the master branch. Issue to change that is here.

So when we went to run a production deploy, we deployed the latest version from staging, which was 1.0.13-4. https://github.com/Expensify/Expensify.cash/releases/tag/1.0.13-4

To resolve (without needing to go through QA again), we can:

1. Create a PR from the latest QA'd tag, 1.0.16-0 to staging. (i.e: this PR)

2. Merge this PR to get staging up-to-date with our latest staging version
3. Close the StagingDeployCash to trigger a new production deploy.

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

10 out of 11 committers have signed the CLA.
✅ @jasperhuangg
✅ @parasharrajat
✅ @marcaaron
✅ @Maftalion
✅ @roryabraham
✅ @Jag96
✅ @deetergp
✅ @alex-mechler
✅ @tgolen
✅ @iwiznia
❌ @ctkochan22
_{You can retrigger this bot by commenting recheck in this Pull Request}

[AndrewGable]

Looks good! I don't think GitHub actions is going to be happy with this PR, so I will have to merge with broken CLA checks.

[OSBotify]

🚀 Deployed to staging in version: 1.0.43-9🚀

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

[OSBotify]

🚀 Deployed to production in version: 1.0.44-0🚀

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