[NT-783] Send prelaunch project links to safari instead of opening in the app

[ifbarrera]

📲 What

Fixes a bug where we were incorrectly displaying prelaunch projects in the app when they were accessed through a link in a project update.

🤔 Why

A few months ago we added the "prelaunch" feature to project pages on web. Since native apps don't support prelaunch project pages, we updated our universal link handling for project links to check whether the project was a prelaunch project, and if it was, we send the user to mobile web instead of opening the project page in the app.

However, we missed adding this check in the UpdateViewController, which supports opening project links natively in the app. This meant that it was possible for a user to tap on a prelaunch project link from a project update and be presented with an incomplete project page natively.

🛠 How

We now check whether the project is a prelaunchActivated project before presenting the project page natively. If the project is a prelaunch project, we load the project url in a safari webview. If the project is not a prelaunchActivated project, then we present the native project page as before.

One thing I noticed which wasn't great is that project links make a network request but give no indication to the user that something is happening (ie. we don't show a loader). This can make it seem like opening the link is "hanging" when in fact a request is being made.

👀 See

✅ Acceptance criteria

This can only be reliably tested by building a Release configuration of the app on a device, then doing the following:

• Search for the project "Ark Worlds: MOBA Card Game", then tap "Updates" and click on the first one called "Prelaunch page is up". Then, click on the link on the update. The link should open in a safari webview that's presented modally

[Scollaco]

Looks good ⭐️