fix(offline-support): foreign constraint failure

[santhoshvai]

🎯 Goal

To fix foreign key constriant failure

upsertMessages touches three tables: 1. messages 2. users 3. reactions.. so either of these foreign key fails

• table: messages - foreign_key: [cid]
• table: users - foreign_key: []
• table: reactions - foreign_key: ['messageId', 'userId']

cases of failure

1. a message update from BE without the channel being in our local DB -- from channel hide
2. a message update from BE but the reaction's user or message is not in the local DB -- due to wrong order where reactions are upserted before users

🛠 Implementation details

case 1: add the channel again to DB before inserting the message
case 2: correct the order -- this was unknowingly already fixed in 5.26!

🧪 Testing

• Send a message to a channel that is hidden for a member from other member in the channel

☑️ Checklist

• I have signed the Stream CLA (required)
• PR targets the develop branch
• Documentation is updated
• New code is tested in main example apps, including all possible scenarios
  • SampleApp iOS and Android
  • Expo iOS and Android

[stream-ci-bot]

🎉 This PR is included in version 5.27.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀