This PR succeeds#123402 and reworks the approach to use the eval breaker for the invalidation call instead of executor creation or gc (thanks@markshannon!). In experimenting, I tried a couple of different thresholds of 10k, 100k, and 1 million runs. The benchmarks for100k and1 million were most promising. Here are some relevant stats for quick reference:

100k
--2.4% memory
-Roughly the same performance-wise

1 million

• -1.5% memory
• Roughly the same performance-wise

After chatting with@brandtbucher, I've opted to open this PR with the 100k threshold. One thing to note is that we are potentially a little too liberal in invalidating executors with this threshold, but with the lack of movement in performance and a more substantial decrease in memory usage, it seemed justified. We can continue to iterate here and consider making this tunable in the future.

• Issue:Improve JIT memory consumption by invalidating cold executors #123516