feat: restrict login to different backend (WPB-26152)

[sbakhtiarov]

https://wearezeta.atlassian.net/browse/WPB-26152

https://wearezeta.atlassian.net/browse/WPB-26152

What's new in this PR?

Restrict users login to backend which is different from current session backend

• New feature flag to enable the feature
• KaliumConfigs update to expose the flag to kalium use cases
• Call new use case in regular and SSO login flows.

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.92%. Comparing base (e16d539) to head (5ccedba).

Files with missing lines	Patch %	Lines
...otlin/com/wire/android/ui/WireActivityViewModel.kt	50.00%	5 Missing and 3 partials ⚠️

❌ Your patch check has failed because the patch coverage (50.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4957      +/-   ##
===========================================
- Coverage    48.93%   48.92%   -0.01%     
===========================================
  Files          643      643              
  Lines        23055    23068      +13     
  Branches      3521     3525       +4     
===========================================
+ Hits         11282    11287       +5     
- Misses       10727    10732       +5     
- Partials      1046     1049       +3     

Files with missing lines	Coverage Δ
...rc/main/kotlin/com/wire/android/ui/WireActivity.kt	0.00% <ø> (ø)
...otlin/com/wire/android/ui/WireActivityViewModel.kt	69.58% <50.00%> (-0.87%)	⬇️

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e16d539...5ccedba. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

@sbakhtiarov looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop	This PR
3a39fb17538cef4c96eee5459cf9707924889a24	2b359bdcca5a2696dcc8e2c8729329d9aaacabec

Is this intentional?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud