Wrong overshoot speed after settling keyframe

[zsoltk]

Scenario:

1. Pass animateSettle = true to a created InteractionModel instance.
2. Test keyframe mode with button + also with dragging

ER: the keyframe settles with an overshoot that's in harmony with the visually observed speed when reaching the target
AR: video

overshoot.mov

[zsoltk]

Might be a combination of two problems:

1. Android doesn't seem to have this problem, but in fact it does (after spamming the buttons a few times), it's just that the overshoot is super minimal (whether actually that's the expected behaviour or the no overshoot is something to be established)
2. Since the velocity calculation depends on measuring time elapsed, and we have clock / platform, the web version might be off by some order of magnitude, causing the same issue to have a much more emphasized visual effect

cc @manuel-martos re: clock