[WIP][SPARK-3795] Heuristics for dynamically scaling executors

This is part of a bigger effort to provide elastic scaling of executors within a Spark application ([SPARK-3174](https://issues.apache.org/jira/browse/SPARK-3174)). This PR does not provide any functionality by itself; it is a skeleton that is missing a mechanism to be added later in [SPARK-3822](https://issues.apache.org/jira/browse/SPARK-3822).

The design doc can be found at [SPARK-3174](https://issues.apache.org/jira/browse/SPARK-3174) (under "Heuristics for Scaling Executors". This deviates from the design in two ways: (1) the remove policy is significantly simplified by cutting out the exponential increase logic that mirrors the add policy, and (2) the configuration of the add policy is split up into `addExecutorThreshold` and `addExecutorInterval`. The main reason for this is that the user may want to configure how quickly executors are added, but want to keep the trigger condition the same.

Comments and feedback are most welcome, but please keep in mind that this is still WIP! For those of you reviewing this in detail, I highly recommend doing it through your favorite IDE instead of through the diff here.
I also wonder if the word "timer" should not be used here. To me "timer" means a clock that is counting up or down as time passes. Here it means an absolute time at which an event should trigger. I think in reality "timer" can mean both things (http://www.merriam-webster.com/dictionary/timer), but it might be good to avoid the name.