Precommit could check for any tests in the latest commit and do a cursory beasting. [LUCENE-8545]

Many tests are not currently beastable with the build beast target because they are not made in a way that they can be called repeatedly with a clean env.

We should consider letting precommit lightly beast any test in the last commit - this will ensure tests can be beasted with the build beaster and gives a little protection against some of the really flakey tests that get committed.

I have a little prototype that still needs a bit of work.

---
Migrated from [LUCENE-8545](https://issues.apache.org/jira/browse/LUCENE-8545) by Mark Miller (@markrmiller)
Linked issues:
- [SOLR-12801](https://issues.apache.org/jira/browse/SOLR-12801)
- #9593
- [SOLR-12923](https://issues.apache.org/jira/browse/SOLR-12923)
- #9587

Start by examining the precommit workflow, the build beast target, and the existing prototype mentioned in the issue. Determine how tests from the latest commit can be run repeatedly in a clean environment; done means precommit lightly beasts those tests without introducing flaky or non-repeatable behavior.

Written by the indexing model from the issue text.