* Make sure the logout doesn't cause a crash
Some reasons why this could happen:
1. The `ClientDelegate` could receive a `didReceiveAuthError` callback call on a logout, which could trigger another logout when every Rust object had already been destroyed.
2. Even though we stop the sync before logging out, `LoggedInFlowNode` will try to start it again automatically when it detects we still have internet connection.
Making sure to unregister the delegate should fix the first part of the issue.
For the other one, adding `RustSyncService.isServiceReady` to check if we should start/stop the service, which is enabled by default and set to false on destroy should help.
* Apply the same patch on account deactivation.
---------
Co-authored-by: Benoit Marty <benoit@matrix.org>
8c2a6a54af