BREAKING CHANGE: hoist the responsibility of sharing local memory cache adapter into application

[wschurman]

Why

Closes ENG-6773.

The responsibility of defining the scope of how broadly or narrowly the shared cache should be shared should be the responsibility of the application. This way, the application can decide to share it amongst all requests or just have it be per-request (unlikely, but shouldn't be dictated by library).

Ref: https://github.com/expo/universe/pull/10701#pullrequestreview-1143120207

How

Make localMemoryCacheAdapterMap per-instance of the LocalMemoryCacheAdapterProvider. Applications should create one instance of this provider per shared scope.

Test Plan

Run tests.

[linear]

ENG-6773 Fix LocalMemoryCacheAdapterProvider shared state

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ef7b452) 95.46% compared to head (3297d37) 95.46%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #218      +/-   ##
==========================================
- Coverage   95.46%   95.46%   -0.01%     
==========================================
  Files          79       79              
  Lines        2075     2074       -1     
  Branches      258      258              
==========================================
- Hits         1981     1980       -1     
  Misses         93       93              
  Partials        1        1              

Flag	Coverage Δ
integration	95.46% <100.00%> (-0.01%)	⬇️
unittest	95.46% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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