fix: wrong migrations order between 4.9 and 4.10 [WPB-15157] 🍒

[github-actions]

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

• fix: wrong migrations order between 4.9 and 4.10 [WPB-15157] #3238

Original PR description:

---

WPB-15157 App crashes after receiving links in a group chat

---

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 cherry-picking the fix for multiple mentions from 4.9 to RC 4.10, the order of migrations were changed - in 4.9 migration related to this fix was added as 91.sqm but in 4.10 as 95.sqm, so it means that when updating the app from 4.9 to 4.10, the app will lose migration that's implemented in 4.10 as 91.sqm because migration with number 91 has already been executed in 4.9.

Solutions

Migration from 91.sqm is about creating ConversationFolder and LabeledConversation, so to fix it, additional migration 96.sqm was created in order to add these tables if they don't yet exist.
Note: this new migration also needs to be added to dev (4.11) to maintain the order there.

---

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.

[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