Stop loading default chat room initally for those outside of beta

[TomatoToaster]

@deetergp, please review when you get the chance
CC: @yuwenmemon

Details

There was an edge case we didn't consider when putting default rooms behind betas. If a domain has a domainAll room (which we make behind the scenes for domains that aren't in the defaultRooms beta) and a user gets created after that room is made, they will actually see that room when they first log in (i.e. it'll be their "last accessed chat report"). They should see the concierge chat first, but that chat will be created after their account is made (which happens after the domainAll room was made).

This PR makes it so new users won't land on a default domainAll room the first time they log in. This also prevents users from seeing a default room if they aren't in the beta and somehow managed to open a default chat room (to stop other edge cases we might have missed.

Also this is relevant to N6, since we're likely to see a lot of new users sign up and use NewDot with this.

Fixed Issues

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

Tests

Same as Web QA, but done locally. I used clitools.sh for making the domain, admin account, and second account. To test a user being outside of the default rooms beta locally, I made this line false:

App/src/libs/Permissions.js

Line 51 in 0e6fdbf

return _.contains(betas, CONST.BETAS.DEFAULT_ROOMS) || canUseAllBetas(betas);

QA Steps

1. Find a domain whose users won't be in the freePlan beta.
2. Invite a new account to that domain (can be similar to amal+something@expensifail.com). Avoid signing in with the email sent to the newly created user.
3. Log into that account on NewDot before joining on OldDot. You can do this by entering the email in NewDot and then using the magic sign in link from there. You might have to set a password at this point too.
4. Verify that the first report you see is the concierge one and not

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

This is what it looks like now if you try to access a report by URL (11073 is a domainAll room)

Mobile Web

Same thing is a blank screen on mobile obviously, but users should never be able to see this report anyway without manually entering into the url like I did.

[deetergp]

LGTM

[OSBotify]

🚀 Deployed to staging by @deetergp in version: 1.0.99-8 🚀

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

[OSBotify]

🚀 Deployed to production by @Jag96 in version: 1.1.0-2 🚀

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