feat(cache): add cleanup callback to LruCache and TtlCache

[WasixXD]

Closes #6851

This PR adds a option: { onEject: (ejectedKey: K, ejectedValue: V) => void) } param to LruCache and TtlCache constructor.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.10%. Comparing base (4595316) to head (da8599c).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6857   +/-   ##
=======================================
  Coverage   94.09%   94.10%           
=======================================
  Files         578      578           
  Lines       42654    42676   +22     
  Branches     6781     6784    +3     
=======================================
+ Hits        40136    40159   +23     
+ Misses       2467     2466    -1     
  Partials       51       51           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lionel-rowe]

Hmm, could work, I think it depends less on cleanness of the interface, and more on whether setting/changing/adding (/removing?) eject handlers after creation is a useful feature and/or a footgun. Also what should this do?

const cache = new LruCache(n)
    .onEject(() => console.log(1))
    .onEject(() => console.log(2))

[WasixXD]

Also what should this do?

As for now, this would just print 2

more on whether setting/changing/adding (/removing?) eject handlers after creation is a useful feature and/or a footgun

I can't think in a scenario where this would be bad

[kt3k]

The main idea looks good to me.

I changed from a options param to a method because i think is cleaner, but I'm not attached to it.

I'd prefer this to be an option instead of a method. Making it an option would make it clearer that it only handles a single callback, not multiple ones.

[WasixXD]

I'd prefer this to be an option instead of a method. Making it an option would make it clearer that it only handles a single callback, not multiple ones.

🫡

[kt3k]

Thanks for updating! LGTM