Fix: disable hardware acceleration when GPU driver crashed the game last attempt

[TrueBrain]

Motivation / Problem

We have a slow but steady report of "game crashes on startup" over the last few months. All these cases come down to:

• We start the OpenGL driver
• The driver crashes for one reason or the other

This leaves the user confused, and they have to dig through tons of things to find out they have to add -v win32 to start the game. Only then they can disable hardware acceleration.

I was wondering: can't we detect if we crashed, and on next start, disable hardware acceleration for the user?

Fixes #10463
Fixes #10394
Fixes #10571

Description

I build this PR on the assumption that Start() causes the driver crash. A few backtraces show this is the case, but a few others we cannot decode; so I am not sure this covers all cases. It might still happen that a crash happens when we actually start drawing for the first time, but we can always extend this code to that later on. For example, by waiting for the first tick to remove the detection file.

Either way, this PR creates a file hwaccel.dat when starting with hardware acceleration. As soon as the first drawing tick finishes, we remove it again. If we try to initialize the video driver with acceleration while that file exist, it means we must have crashed last time. We then disable hardware acceleration.

PS: some changes recently caused those video-driver errors to no longer show up, as they weren't marked critical (any more). I fixed that while I was here. No clue what happened exactly; it used to work, it no longer does, it does now again. shrug

Limitations

Ideally, we find out what gets those drivers to crash; but that has turned out to be very difficult, and often just: known driver bug. Some people seem to never update their drivers, other GPUs haven't release a new drivers in months, and just randomly crash.

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, gs_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

[glx22]

Can't really test myself, but it makes sense.