feat: use storage and invalidation

[simone-sanfratello]

proposal for use of an external storage, with optional invalidation

---

TODO

• [x] test on storage/s
• [x] 100% coverage (and significant cases)
• [x] use an empty logger on storage
• [x] fix CI, add a redis instance
• [x] restore expiration logic on memory storage / do not use Date.now
• [x] expose explicit "invalidation" function
• [x] improve redis storage (pipeline etc)
• [x] storage gc function
• [x] memory storage with sync deletes
• [x] redis storage with sync deletes
• [x] optional invalidation
• [x] benchmarks
• [x] redis references TTL
• [x] redis gc
• [x] "stale-on-error" > next
• [x] solve TODOs
• [x] check redis pipeline
• [x] memory references: use a btree? a set? arrays are good enough
• [x] example
  • [x] basic
  • [x] mjs
• [x] update documentation

[simone-sanfratello]

still have to write test on storage and reach 100% coverage

[mcollina]

great work!

[simone-sanfratello]

I'm collecting on top all the points still have to work a lot on redis :) and on gc

[simone-sanfratello]

@mcollina wait to review, still a wip

[mcollina]

looks good!

[simone-sanfratello]

This needs lots of docs, specifically how to use references

I'm thinking of doing am extended use case in mercurius/cache and link there for documentation, for 2 reason: it's hard to explain references talking with abstractions, and the result of documentation here would be very close to the mercurius/cache one

wdyt?

[mcollina]

Just do one and copy it over/adapt here. I think this deserves some docs anyway.

[simone-sanfratello]

@mcollina apart of documentation, the code is done there are some points in the code marked with TODO, we can probably check them later I'm writing doc for mercurius-cache for references and invalidation, then I'll port here

[simone-sanfratello]

@mcollina done!