Follow-up from "Speed up tests runtime": reduce HIGHEST_OUTPUT_REFRESH usage

The following discussion from !1405 (merged) should be addressed:

• @pq started a discussion: (+3 comments)

  I'd rather the test suite defaults to repaint-only-on-capture, and then test fixtures that need a timed cadence override that explicitly. That way we get a good picture of which tests might be timing sensitive and/or could be fixed to not need it.

  To me the main point of this MR is stop using an arbitrary timeout and just run as fast as the CPU goes whenever possible.

There are tests that really need HIGHEST_OUTPUT_REFRESH and then there are those who should not need it (work by repaint on capture only) but for some reason still wait for frame callbacks. See the above thread for more details.

Go through each test and drop HIGHEST_OUTPUT_REFRESH if possible by adjusting code to not need to wait for frame callbacks anymore and rely on screen capturing instead.