Real-world testing with jcstress frequently runs into capacity problems. There are usually tons of tests in the suite, and there are many JVM options that default runner is traversing by default. This often comes as a nasty surprise for the testers, when the full run starts taking months.

There are "run profiles", selected with `-m`, which are supposed to help here, but they are not that handy to use, and are following the hand-selected hard-coded settings in the harness options.

Instead, we can do a better thing: introduce the "run time budget" option, where a user can say "I have around X hours to run these tests, figure out the best test configuration to fit this time".

This would make jcstress naturally usable in nightly runs, where we can ask for 1 hour run, weekly runs, where we can ask for 8 hour run, monthly runs, where we can ask for 24 hours run.