Improve loop timing and revisit LoopModes

[mitchmindtree]

This is a reminder for myself to revisit our approach to application loop timing, and perhaps implement some options based on the game loop article here.

Options that we definitely want:

• Loop once: model runs once, update runs once then view runs once. Following this, the application simply waits on window, application and input events. update and view are never called again. This would be best implemented a manner that allows any number of loops. Our LoopMode::NTimes is basically this.
• Wait: model runs once, update runs once then view runs once. Following this, the application waits on window, application and input events. Once events are cleared, update and then view run, and the application goes back to waiting for events. This is currently implemented as LoopMode::Wait.
• A continuous loop mode: We currently have RefreshSync and Rate modes, but both are a little unstable on different platforms. This article describes a nice solution which may solve the issues that we currently have with both.

[foltik]

This article might be useful as well: https://gafferongames.com/post/fix_your_timestep/

[bluelhf]

This seems like an integral part of Nannou... As it stands, the Rate mode does not even follow the user preference for a given update rate. It's been two years — are there still plans to work on this?