olm try to decrypt with recent session first

[BillCarsonFr]

Type of change

• Other :quick perf

Content

When we receive an encrypted to device, the SDK has to try to decrypt with all the known endToEnd olm session with the sender, until it founds one working.
According to some android logs, we can see as much as 300 olm session with the same device. This is not expected and probably due to some race issue but none the less currently we are trying to decrypt with all of them but in the wrong order, leading to lot of unnecessary trials. By using proper order we will now decrypt to devices faster.

This PR is not adressing the proliferation of olm session. This PR should have adressed this, and the existing logs are probably from older sessions.

Motivation and context

Screenshots / GIFs

Tests

• Step 1
• Step 2
• Step ...

Tested devices

• Physical
• Emulator
• OS version(s):

Checklist

• Changes has been tested on an Android device or Android emulator with API 21
• UI change has been tested on both light and dark themes
• Accessibility has been taken into account. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#accessibility
• Pull request is based on the develop branch
• Pull request includes a new file under ./changelog.d. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#changelog
• Pull request includes screenshots or videos if containing UI changes
• Pull request includes a sign off
• You've made a self review of your PR
• If you have modified the screen flow, or added new screens to the application, you have updated the test UiAllScreensSanityTest.allScreensTest()

[github-actions]

Unit Test Results

118 files  ±0  118 suites  ±0   1m 30s ⏱️ -11s
203 tests ±0  203 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
682 runs  ±0  682 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 50a4d2b. ± Comparison against base commit cd52df5.

[bmarty]

LGTM, thanks!