Reduce frequency of timeout checks by 10+ times

[adrian17]

In some games (meat boy) instant::now() was taking 10+% of tick time (and that wasn't even the full recorded overhead of the check), so this still needed to be tuned down. In the future, if other actions become faster, this might need to be tuned down even more.

Why "10+ times"? Because if a small function runs between 200 and 2000 actions, its # of checks will drop to 0.

That raises a side question: should actions_since_timeout_check be stored in Context instead of Activation? In practice, I feel like this isn't an issue, as even if an inifinite loop span across a deep call stack, the outermost frame with the loop will amass 2000 actions at some point, right? So the current approach of storing in Activation might even be better as it decreases the frequency of checks without making them weaker.

Alternatively, just put it in Context and bump the number even more.

[Herschel]

Thanks! My instinct is that this would be better in Context, but probably not a huge deal, as you mention. Wondering if we should also up the default timeout from 15s as well as we sadly hit this quite often on some machines/content.