[MS-1300] Sync architecture revamp, part 3

[alex-vt]

JIRA ticket
Will be released in: 2026.2.0

Boundaries for the changes - what's intentionally out of scope:

• WorkManager and workers. This is already the optimal foundation for sync - both foreground and background.
• SyncInfoViewModel. Already observes sync state.
• UI/UX. Nothing visually new.

Notable changes

• (Phase 1) (Done) SyncOrchestrator.observeSyncState implementation.
• (Phase 2) (Done) SyncOrchestrator.execute implementation.
• (Phase 3) (This) SyncOrchestrator.execute cleanup - a lot of call sites involved, making it a small yet separate phase to keep changes focused.
• (Phase 4) (Next) Extracting usecases from SyncOrchestrator & EventSyncManager.

Testing guidance

Note: Infra Unit Tests 1 may be failing due to an unrelated issue unless main with a fix is merged into the current branch.

• Sync counters and buttons on dashboard, sync info and logout screens should work correctly.
• Some SyncOrchestrator.execute calls were changed in other places - full regression testing recommended when the work is completed.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)