Use the simple `decrypt` instead of the sequential one. This might cause some messages to arrive in an inverted order, and we're planning to handle this here: https://linear.app/comm/issue/ENG-8752/update-the-reducers-to-respect-properties-timestamps[ENG-8715](https://linear.app/comm/issue/ENG-8715/stop-requiring-sequential-messages).
https://linear.app/comm/issue/ENG-8715/stop-requiring-sequential-messagesThis differential is doing two things:
1. Renaming `decryptSequentialAndPersist` -> `decryptAndPersist` in `OlmAPI` to properly reflect what this code method is now doing.
2. Using `decrypt` instead of `decrypt_sequential` from `olm` which is an actual change, stops requiring sequential messages.
Depends on D12747This might cause some messages to arrive in an inverted order, and we're planning to handle this here: https://linear.app/comm/issue/ENG-8752/update-the-reducers-to-respect-properties-timestamps
NOTE: This change is not revertable (in logic meaning), in the future if we want to start requiring sequential messages we'll need to reset the `olm` session.