refactor: rename GetUpdatedSelfTeamUseCase to SyncSelfTeamInfoUseCase [WPB-21894]

[MohamadJaara]

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

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

getting user self team info is always waiting on a remote sync of the team data which can block some screens from loading untill we have the whole informations

Solutions

in almost all cases where we need self team we also need self user and there is already a use case for this
also add a seperated usecase for the sync of self team in case we need to trigger it in async in some screens

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[codecov]

Codecov Report

❌ Patch coverage is 96.87500% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 48.65%. Comparing base (7ceee93) to head (b8a641f).
⚠️ Report is 2 commits behind head on develop.

Files with missing lines	Patch %	Lines
...oid/ui/home/settings/account/MyAccountViewModel.kt	90.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4570      +/-   ##
===========================================
+ Coverage    48.60%   48.65%   +0.04%     
===========================================
  Files          576      576              
  Lines        19931    19942      +11     
  Branches      3339     3335       -4     
===========================================
+ Hits          9688     9702      +14     
  Misses        9214     9214              
+ Partials      1029     1026       -3     

Files with missing lines	Coverage Δ
...tions/details/GroupConversationDetailsViewModel.kt	89.43% <100.00%> (+2.65%)	⬆️
...id/ui/userprofile/self/SelfUserProfileViewModel.kt	58.04% <100.00%> (+1.52%)	⬆️
...oid/ui/home/settings/account/MyAccountViewModel.kt	89.83% <90.00%> (+0.73%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ceee93...b8a641f. 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]

@MohamadJaara 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
0ac7c385b7dbbf9334125ff4eae9636d212134ad	8478f6d491e7f73df805a6452f0500da6b6af75c

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