Add a SignOutFlowPresenter.

[pixlwave]

This PR pulls together some logic that has been implemented in both All Chats and Settings and was needed in the new Device Manager. The presenter shows the signout alert but also follows through and shows the relevant key backup screens too if they're needed rather than leaving this to the individual screens to handle themselves.

Note: Whilst TabBarCoordinator also contains this same flow, it doesn't really need to anymore and will be handled as part of #6853.

All screens

[github-actions]

📱 Scan the QR code below to install the build for this PR.
🔒 This build is for internal testing purpose. Only devices listed in the ad-hoc provisioning profile can install Element Alpha.

If you can't scan the QR code you can install the build via this link: https://i.diawi.com/MJ7YHL

[codecov]

Codecov Report

Base: 11.58% // Head: 11.62% // Increases project coverage by +0.03% 🎉

Coverage data is based on head (2d6419b) compared to base (3133317).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6854      +/-   ##
===========================================
+ Coverage    11.58%   11.62%   +0.03%     
===========================================
  Files         1553     1560       +7     
  Lines       154845   155209     +364     
  Branches     62471    62651     +180     
===========================================
+ Hits         17946    18044      +98     
- Misses      136292   136554     +262     
- Partials       607      611       +4     

Impacted Files	Coverage Δ
...ot/Modules/Home/AllChats/AllChatsCoordinator.swift	24.65% <0.00%> (+2.49%)	⬆️
Riot/Modules/Settings/SettingsViewController.m	0.00% <0.00%> (ø)
...odules/Settings/SignOut/SignOutFlowPresenter.swift	0.00% <0.00%> (ø)
...ions/Coordinator/UserSessionsFlowCoordinator.swift	0.00% <0.00%> (ø)
...ons/UserOtherSessions/View/UserOtherSessions.swift	53.57% <0.00%> (-25.85%)	⬇️
...UserOtherSessions/UserOtherSessionsViewModel.swift	63.52% <0.00%> (-17.61%)	⬇️
...erSessionsOverview/View/UserSessionsOverview.swift	78.36% <0.00%> (-7.61%)	⬇️
...ogin/Common/Service/MatrixSDK/QRLoginService.swift	11.63% <0.00%> (-7.41%)	⬇️
...t/Modules/Rendezvous/MockRendezvousTransport.swift	67.64% <0.00%> (-6.55%)	⬇️
...view/View/UserSessionListItemViewDataFactory.swift	89.70% <0.00%> (-5.21%)	⬇️
... and 26 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[Anderas]

I don't mind this approach with independent protocol methods, though I thought we mostly use ViewModels/ViewStates with individual .loading, .loaded, .error cases, and single method to dispatch them. I am not suggesting to change it, just wanted to see what you thought about those two approaches

[pixlwave]

So I started with a callback and the cases you described as I'd much prefer that. But then I needed to switch to the delegate when integrating the presenter into the SettingsViewController as the .error case couldn't have an associated value and also be compatible with objc.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information