fix: disable import media during slow sync [WPB-15790]

[Garzas]

WPB-15790 [Android] Client created a second conversation when sharing an image through share extension

---

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

• There is a race condition where sharing an image via the share extension during slow sync could send message to already migrated 1:1 conversation.

Causes (Optional)

• The temporary inconsistency in conversation resolution led to a state where multiple 1:1 conversations were displayed across different clients.
• Eventually, the duplicate conversation was removed after a delayed sync resolution, but it caused confusion and message loss.

Solutions

• Introduced SyncStatusViewModel to track the sync state and prevent sending media when slow sync is in progress.
• Disabled the send button (loading state) until slow sync completes, ensuring that messages are only sent to a fully resolved conversation.

Attachments (Optional)

[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

[github-actions]

Built wire-android-staging-compat-pr-3852.apk is available for download

[saleniuk]

There is already a mechanism for blocking button click action while the app is syncing or/and connecting, it's called ClickBlockParams and you just pass it as a button parameter. I can see that this button already has this enabled to block when syncing and when connecting

clickBlockParams = ClickBlockParams(blockWhenSyncing = true, blockWhenConnecting = true),

so it should act like that already if nothing is broken there but I can see that it's working, so changes from this PR are likely to be redundant 🤔