Vulkan-compatible implementations should pass Vulkan validation layer checks

e.g. SteamVR generates numerous validation layers on startup and more every frame, causing undefined behavior and making it difficult to distinguish genuine application bugs. This could be mechanically validated by configuring [a Vulkan debug messenger](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#debugging-debug-messengers), running through a few frames (if not the entire test suite), and failing the test if when an error is reported to the callback. The Vulkan validation layers should be configured for maximum strictness (e.g. synchronization validation, GPU-assisted).

Start by locating the conformance tests that create Vulkan instances and run frames. Configure a Vulkan debug messenger with maximum-strictness validation, including synchronization and GPU-assisted validation, then run several frames or the test suite. Done means validation errors reported to the callback cause the test to fail.

Written by the indexing model from the issue text.