[d3d9, regression] Myst V freeze/crash upon resolution change

[Blisto91]

When attempting to change resolution in Myst V the game will error "initializing your video card" and then freeze until you restart the game
Bisected to start with either 52ac271, 8f740c5 or b8d36ee. Two commits had to be skipped since the game wouldn't start with them.

d3d9.countLosableResources = False works around the issue.

Software information

Myst V

System information

• GPU: RX 7900 xtx
• Driver: mesa main
• Wine version: Proton Bleeding Edge

Apitrace file(s)

https://drive.proton.me/urls/Y3Y418SP34#esWLnSJGvH9E

Log files

steam-208110.log

[K0bin]

This looks like a game bug. Replaying the apitrace with native D3D9 fails the reset call just like DXVK does.

[Blisto91]

Checking the game on Windows it doesn't crash natively, but it does still crash with dxvk there. It seems like apitrace itself might not like the event where it switches resolution as even a native captured trace will crash in that spot when replayed on Windows

[K0bin]

An apitrace made with the Nvidia D3D9 driver on Windows also fails when replaying it with the very same Nvidia D3D9 driver on Windows. Same issue as DXVK. So I guess we should just disable the losable counting for the game...

[Blisto91]

Worked around via #4051