BeatMap: Fix bpm and sync behavior with beatmaps.

YOUR BPM INDICATOR IS LYING TO YOU.  Since a beatmap
doesn't have a constant bpm, using the "file_bpm" value
for sync and slider display is misleading.  This commit introduces
a new ControlObject, "local_bpm", which represents the average
bpm value around the closest 8 beat span.  It's still a fairly
noisy value, so it may require tuning.  This local_bpm
value is used to display the visual_bpm, so now you can
watch the bpm of your crazy track change over time.  Also it's
used for master sync, so you can watch the pitch slider
of your track wobble around as it tries to stay in sync.

TESTED=existing tests pass, and some new tests for the bpm averaging function.
I think the direction of travel matters more than what's behind you. What about 2 beats behind and 6 ahead (forwards or backwards based on whether you're in reverse). 

Or only look in the direction of travel and not behind you. When you cross a drop-boundary and the BPM halves the beats behind you shouldn't matter anymore?