change(notification_client): use cross process locking event and media stores instead of in-memory ones

[stefanceriu]

This will allow the NSE process to populate the event cache store with even data after retrieving it from sync, as opposed to dropping after rendering the notification it as it did previously.

[codecov]

Codecov Report

❌ Patch coverage is 85.00000% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.94%. Comparing base (fbff1ee) to head (e98e4f5).
⚠️ Report is 66 commits behind head on main.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
crates/matrix-sdk-base/src/client.rs	75.00%	6 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5934   +/-   ##
=======================================
  Coverage   88.93%   88.94%           
=======================================
  Files         357      357           
  Lines       99195    99219   +24     
  Branches    99195    99219   +24     
=======================================
+ Hits        88224    88247   +23     
- Misses       6987     6990    +3     
+ Partials     3984     3982    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will not alter performance

_{Comparing stefan/notificationClientCrossProcessLockingStores (e98e4f5) with main (fbff1ee)}

Summary

✅ 50 untouched benchmarks

[Hywan]

⚠️ This is wrong!

You're cloning the EventCacheStoreLock and MediaStoreLock, with the main cross-process holder name. It doesn't use the new cross_process_store_locks_holder_name received by argument here.

[Hywan]

@stefanceriu if you want to give another try, have fun!

[stefanceriu]

Turns out this doesn't actually work and we probably do need the state store cross process lock. Will raise again once we're ready to do this properly.