Instead of iterating over all origin visits to find the one we are insterested in.in, Inuse a
simpler storage api call. In case of a huge number of visits for an origins, this makes the resolution spin out of
control until a crash.
wip because tests need to be adapted (drop mocks, simplification...the resolution spin out of control until it crashes (when the cache is initially empty).
Related to T3905