Fix #10079: don't render at 1000fps if HW acceleration + vsync is requested but not active

[TrueBrain]

Motivation / Problem

Fixes #10079.

When you enable HW acceleration in-game, you get told to restart. But if you don't ....... you can also enable vsync, and the game actually tries to align with vsync. But there is no vsync in non-HW accelerated backends. So it just goes to 1000fps.

Description

Query the driver to know whether it is hw-accelerated.

Sadly, this information was currently only available in the DriverFactoryBase, so it had to be duplicated into the VideoDriver to be available (in quick way) for GetDrawInterval.

Limitations

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

• The bug fix is important enough to be backported? (label: 'backport requested')
• This PR touches english.txt or translations? Check the guidelines
• This PR affects the save game format? (label 'savegame upgrade')
• This PR affects the GS/AI API? (label 'needs review: Script API')
  • ai_changelog.hpp, game_changelog.hpp need updating.
  • The compatibility wrappers (compat_*.nut) need updating.
• This PR affects the NewGRF API? (label 'needs review: NewGRF')
  • newgrf_debug_data.h may need updating.
  • PR must be added to API tracker

[rubidium42]

When the vtable is too slow, one can always consider making it an instance variable of VideoDriver and setting that in the constructor.

[TrueBrain]

When the vtable is too slow, one can always consider making it an instance variable of VideoDriver and setting that in the constructor.

Not sure that is actually an improvement, but for visibility, pushed it nevertheless.