Don't report violations of VUID-vkCmdEndDebugUtilsLabelEXT-commandBuffer-01912

[jimblandy]

As described in Vulkan-ValidationLayers#5671, the validation layers don't understand debug ranges paired across different command buffers on the same queue, even though the Vulkan spec says:

An application may open a debug label region in one command buffer and close it in another, or otherwise split debug label regions across multiple command buffers or multiple queue submissions. When viewed from the linear series of submissions to a single queue, the calls to vkCmdBeginDebugUtilsLabelEXT and vkCmdEndDebugUtilsLabelEXT must be matched and balanced.

Until this is fixed, wgpu should ignore this validation error to reduce noise in test runs.

Fixes #3733.

Checklist

• Run cargo clippy.
• Run RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown if applicable.
• Add change to CHANGELOG.md. See simple instructions inside file.

[jimblandy]

Layer properties in KhronosGroup/Vulkan-ValidationLayers@a90644606 (after introduction of 01912 test):

LayerProperties {
    layer_name: "VK_LAYER_KHRONOS_validation",
    spec_version: 4206832, // 1.3.240
    implementation_version: 1,
    description: "Khronos Validation Layer",
}

[jimblandy]

Layer properties in KhronosGroup/Vulkan-ValidationLayers@a54744d67 (current main):

JIMB: instance layer: LayerProperties {
    layer_name: "VK_LAYER_KHRONOS_validation",
    spec_version: 4206842, // 1.3.250
    implementation_version: 1,
    description: "Khronos Validation Layer",
}

[jimblandy]

Okay, this version of the PR supplies the validation layer description and version to the debug utils messenger callback, and checks them to ensure that we're only filtering out errors from affected versions of Vulkan-ValidationLayers.

But I think it does violence to the API of vulkan::Instance::from_raw, so I want to look at it again tomorrow.

[cwfitzgerald]

Would be great to get this in as #3830 is now hitting it.

[cwfitzgerald]

Nice!