fix: messages migration from proteus to mls [WPB-15149] 🍒

[github-actions]

WPB-15149 [Android] App is stuck after MLS migration

This PR was automatically cherry-picked based on the following PR:

• fix: messages migration from proteus to mls [WPB-15149] #3218

Original PR description:

---

---

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

When moving messages from proteus conversation to MLS if some message contained reactions or RestrictedAsset then migration failed causing slow sync to break.

Solutions

Migrate MessageRestrictedAssetContent and Reaction tables to update on cascade when Message is changing conversation_id

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

1. Before enabling mls add reactions to messages on 1on1 conversation
2. Enable MLS for the team
3. Trigger slow sync on both clients in the same 1on1 conversation
4. App should not stuck on sync and user should see that current 1on1 conversation is using MLS protocol

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]

Test Results

0 tests   - 3 386   0 ✅  - 3 278   0s ⏱️ - 5m 36s
0 suites  -   581   0 💤  -   108 
0 files    -   581   0 ❌ ±    0 

Results for commit 9b8b3a4. ± Comparison against base commit 5788184.

♻️ This comment has been updated with latest results.

[github-actions]

Bencher Report

Branch	fix/messages-to-mls-conv-migration-cherry-pick
Testbed	ubuntu-latest

⚠️ WARNING: No Threshold found!

Without a Threshold, no Alerts will ever be generated.

• Latency (nanoseconds (ns))

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds CLI flag.

Click to view all benchmark results

Benchmark	Latency	microseconds (µs)
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInFiles	📈 view plot ⚠️ NO THRESHOLD	695.25
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInMemory	📈 view plot ⚠️ NO THRESHOLD	327,420.86
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.messageInsertionBenchmark	📈 view plot ⚠️ NO THRESHOLD	1,343,055.27
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.queryMessagesBenchmark	📈 view plot ⚠️ NO THRESHOLD	22,202.08

🐰 View full continuous benchmarking report in Bencher

[datadog-wireapp]

Datadog Report

Branch report: fix/messages-to-mls-conv-migration-cherry-pick
Commit report: 60307b4
Test service: kalium-jvm

✅ 0 Failed, 300 Passed, 13 Skipped, 41.93s Total Time