doc: add Client Main Loop section
This starts a new chapter Implementation Guidelines and Recommendations for us to document how Wayland client (and maybe compositors too) should work.
I got the inspiration for this from the recent game main loop discussions I have had. I have a personal agenda to stop game engines and libraries from relying on blocking window system calls. Such calls are actually hard to use right, because they may block indefinitely on Wayland. It would also be good to do something about the "moar fps" disease that is seen as the solution to all latency problems which in many cases really stem from a poor main loop design. If a game can update its state and handle input faster than a display can display it, then don't draw frames that would only be thrown away.
This doc patch should address the main loop design aspect.
Why blog when you can write docs instead.