Add onboarding deeplinks (invite and redirect)

[TimoPtr]

Summary

LauncherActivity now can be started with a DeepLink sealed interface instance. For now it only support Invite and NavigateTo. I decided to keep the LinkActivity to handle the server selection and potential modification/validation of the data received on the app.

The current state of the navigation framework doesn't allow us to use the deeplink capability since it has too many restrictions. So for now everything is using the startDestination. Unfortunately the sub-navigation-graph cannot read the value from the startDestination, that's why I passed a serverToOnboard parameter to the OnbardingNavigation instead of simply using the route. IMO it is also a valid pattern that I'm going to use to morph the onboarding graph for the wear.

I fixed an issue where when we open the Frontend from the Launcher it was keeping the Launcher in the backstack with a white screen. For now it is a workaround with a dummy route that doesn't do anything except redirecting to the activity and finish the current activity. Later we are going to remove this once the WebViewActivity is using the navigation framework.

Checklist

• New or updated tests have been added to cover the changes following the testing guidelines.
• The code follows the project's code style and best_practices.
• The changes have been thoroughly tested, and edge cases have been considered.
• Changes are backward compatible whenever feasible. Any breaking changes are documented in the changelog for users and/or in the code for developers depending on the relevance.

Any other notes

For now the homeassistant://navigate links are still handled by the WebViewActivity directly.

[github-actions]

Test Results

 85 files   85 suites   9m 0s ⏱️
425 tests 425 ✅ 0 💤 0 ❌
440 runs  440 ✅ 0 💤 0 ❌

Results for commit 8f88829.

♻️ This comment has been updated with latest results.

[jpelgrom]

Testing LinkActivity: while comparing the current production app and this version, this version is noticeably slower than production and has a weird flash at the top of the screen. Both are cold starts (app removed from recents).

Current prod:

deeplink-old.mp4

This version with new deeplinks:

deeplink-new.mp4

[jpelgrom]

After discussion on Discord, I tested a debug build of the latest commit of main and performance/behavior for deeplinks seems similar to this PR branch, so the observed difference is probably because of debug and not the changes in this PR.

deeplink-main.mp4