Allow builds to distribute to external testers

[AndrewGable]

Details

I am curious to see what happens when we have distribute_external set to true and reject_build_waiting_for_review set to false (the default) and we have a build in review. I think it might fail in these instances, but I want to make sure this throws an error only in that case, then in all other cases it does distribute the build to testers.

Fixed Issues

$ #2748

Tests

1. Merge this PR
2. Let's see if the build is available for testers to use immediately (it should be)
3. When a new version is submitted, let's make sure it's put into review (it should be)
4. Let's watch and see what happens when another build is submitted when 3 is in review (it might error, but let's see)

[github-actions]

⚠️ ⚠️ Heads up! This pull request has the CP Staging label. ⚠️ ⚠️
Merging it will cause it to be immediately deployed to staging, even if the open StagingDeployCash deploy checklist is locked.

[AndrewGable]

Merging to CP to start testing.

[OSBotify]

🚀 Cherry-picked to staging by @AndrewGable in version: 1.0.90-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

[AndrewGable]

This worked for test step 2 🎉 I will keep an eye on future builds and see if any do not work and fix them when we figure out a case that doesn't work.

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.0.90-2 🚀

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

[OSBotify]

🚀 Deployed to staging by @AndrewGable in version: 1.0.90-3 🚀

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

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.0.91-0 🚀

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

[AndrewGable]

Just confirmed that case 1 is being handled correctly: