Dynamic Index Cache Sizing [LUCENE-10602]

Working with Lucene's filter cache, it has become apparent that it can be an enormous drain on the heap and therefore the JVM. After extensive usage of an index, it is not uncommon to tune performance by shrinking or altogether removing the filter cache.

Lucene tracks hit/miss stats of the filter cache, but it does nothing with the data other than inform an interested user about the effectiveness of their index's caching.

It would be interesting if Lucene would be able to tune the index filter cache heuristically based on actual usage (age, frequency, and value).

This could ultimately be used to give GBs of heap back to an individual Lucene instance instead of burning it on cache storage that's not effectively used (or useful).

---
Migrated from [LUCENE-10602](https://issues.apache.org/jira/browse/LUCENE-10602) by Chris Earle (@pickypg), updated Jun 09 2022

No file or test is named. Start by locating Lucene's filter cache implementation and the existing hit/miss statistics, then review how cache age, frequency, and value could be evaluated. The issue is not done until a specific heuristic, behavior, and corresponding tests are agreed upon.

Written by the indexing model from the issue text.