Submit latest version of EvalTuner and clean up commits

[cryptodeal]

Must have been a bit tired last night because I messed up when merging commits to resolve conflicts; resubmitted with the updated code and cleaned up commit history.

[cryptodeal]

Also, per convo with @bwasti on Discord, I've benchmarked manually calling eval once per iteration during benchmarks as a baseline:

Here's the results w/o any calls to eval:

Here's the performance running the same tests using EvalTuner with StochHillClimb EvalFn:

And here's the performance running the same tests using EvalTuner with Fast EvalFn:

I ran the tests a bunch to tweak/optimize the parameters for the benchmarks (generally solid default params), but for the actual screenshots I ran each of the above once, capturing the result from that initial run to avoid cherrypicking best runs.

[cryptodeal]

Had mistakenly not removed an import for the enum that's been removed as it's no longer used per suggestion in code review; last push fixed it. Will stop working on this pending further feedback.

[bwasti]

Benchmarking on GP100

Baseline:

new EvalTuner(new Fast()):

new EvalTuner(new StochHillClimb()):

[bwasti]

If you give it more time to warm up, the tuner gets noticeably better results:

Baseline:

EvalTuner(Fast):

[cryptodeal]

Going to close so that I can start hacking at this again locally. Will reopen once I've got consistently improved performance out of the algo vs the more hit or miss performance of previous attempts.