The test `on QR code data ready - calls the expected callback` sometimes fails on the CI with the following error:
androidx.concurrent.futures.CallbackToFutureAdapter$FutureGarbageCollectedException: The completer object was garbage collected - this future would otherwise never complete. The tag was: CameraX initInternal
* Fix unverified account after account creation:
When we create an account either using OIDC or by importing a login and password one, we need to wait until the verification state is known (either verified or unverified).
The problem is the verification service will return incorrect values until the E2EE tasks are initialized in the SDK, even if we add the state listeners after doing so.
So what we can do is initialize the E2EE setup, discard any invalid verification state received while it's not initialized, and take only those received after it's initialized.
* Actually restore the `Client` in `RustMatrixAuthenticationService.importCreatedSession` so we don't need to use `clear` and have the navigation restore the client later:
This standarizes the way the login/registration flow works, always restoring/reusing the existing client instance
* Use the SDK `Client` to check whether a HS is compatible
* Remove usage of unused `WellKnown`, keep `ElementWellKnown`
* Make `HomeServerLoginCompatibilityChecker.check` return `true/false` values to distinguish non-valid homeservers from a failed check
* Use `inMemoryStore` and `serverNameOrHomeserverUrl`
* Do some cleanup of `isValid` and `isWellknownValid`
* Make the debounce for starting the search a bit higher, as checking for the homeservers seems more resource-intensive now
* Introduce JsonProvider.
It will ensure that classes are using the correct Json instances in the unit tests.
* Avoid creating a Json instance many times.
* Update ref.
