tests: Fix some tests on Qualcomm.
Do we care about an Adreno 540 with a proprietary driver offering nothing more than Vulkan 1.0 with ridiculously insufficient extensions and features to fully emulate D3D12? Probably not too much. But I argue that it's useful to run our tests there, if nothing else because throwing our Vulkan commands to a wider range of implementations can help us discover more problems (see for example tests: Transition all resources to PIXEL_SHADER_RESOURCE.
in this MR, which actually caused a crash on Qualcomm). Also that GPU, while surely insufficient for many applications, is still able to run simple D3D12 programs, and with the new x86-on-ARM support being added to Wine there are already experiments around to run desktop games on phones. Given that this should not get too much in the way of main desktop development, I see no reason to drop it.