* Add a picker mode to the ServerConfirmationScreen.
* Hook up the account provider picker in authentication the flow.
Simplify the authentication flow coordinator, removing the restricted state.
* UI/Snapshot tests.
* Add support for account provisioning links and route them to the authentication flow.
* Use the provisioning parameters to configure the authentication flow.
* Add UI tests for the provisioned authentication flow.
* Record new preview snapshots.
* Add unit tests.
* Make the domain configurable in the app settings.
* Use the loginHint in the login screen too.
* Add some tests for DeferredFulfillment with Observation.
* Use StateStoreViewModelV2 in AuthenticationStartScreen.
* Use StateStoreViewModelV2 in ServerConfirmationScreen.
* Use StateStoreViewModelV2 in ServerSelectionScreen.
* Use StateStoreViewModelV2 in SoftLogoutScreen.
* Use StateStoreViewModelV2 in SettingsScreen.
* Use StateStoreViewModelV2 in DeveloperOptionsScreen.
* Use StateStoreViewModelV2 in AdvancedSettingsScreen.
* Fetch the OIDC login URL as part of the Server Confirmation screen.
The loading indicator would show and hide while configuring and then immediately show again while fetching the URL.
* Allow the OIDCAuthenticationPresenter to show its own errors.
We no longer need to present errors in the authentication flow coordinator.
* Fail configuration of the authentication service if the homeserver doesn't support login.
* Move the ServerSelectionCoordinator logic into the ViewModel.
- Handle the new login alert.
- Add more tests
* Don't query the homeserver until confirming it (or selecting a different one).
* Setup the infrastructure to test AuthenticationService.
Implement basic tests for configuration & password login.
* Use the real AuthenticationService with a mock Client in all of the tests.
* Add tests for the ServerConfirmationScreenViewModel.
* Remove redundant view state and test for it.
* Replace Rust's Authentication service by building a Client.
* Drop the Proxy from AuthenticationServiceProxy[Protocol].
* Make sure to call abortOIDCLogin.
* Centralise common ClientBuilder code.
* Update the SDK.
* Present OIDC directly on the ServerConfirmationScreen.
Read the actual window from the view.
* Pop back to the confirmation screen when a user enters an MXID that needs OIDC.
* Remove OIDC error handling from the login screen.
