feat: add ability to define a custom cache key invalidation version supplier

[wschurman]

Why

This implements a mechanism so that applications may specify a custom strategy for cache key version invalidation, one example of which is #275 (comment)

How

Add a custom key version supplier function and expand the configuration.

Test Plan

Run the new test.

[wschurman]

• feat: add ability to define a custom cache key invalidation version supplier #290 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b9b0993) to head (51c02f4).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #290   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           80        80           
  Lines         2229      2233    +4     
  Branches       272       273    +1     
=========================================
+ Hits          2229      2233    +4     

Flag	Coverage Δ
integration	100.00% <100.00%> (ø)
unittest	100.00% <100.00%> (ø)

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.

🚀 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.