Enable support for `VK_KHR_ray_query`

[KacperZielinski-Intel]

Description

Enable support for VK_KHR_ray_query, and fix current VK_KHR_acceleration_structure implementation.

This pull request contains minimal functionality set for capturing apps that use VK_KHR_ray_query.

Missing features:

• Shader debugger support for shaders with SPV_KHR_ray_query types.
  Although, disassembly of such shaders is working correctly;
• Support for VK_DESCRIPTOR_TYPE_ACCELERATION_STRUCTURE_KHR descriptors sets in functions:
  • VulkanReplay::PatchReservedDescriptors;
  • VulkanRenderState::BindDescriptorSet;
  • Commands from VK_KHR_push_descriptor extension;
  • Commands from VK_KHR_descriptor_update_template extension;

All lacking features have been "marked" with TODO comments in the codebase.

Known Issues:

• Non-zero captured frames from "Basic ray queries" KhronosGroup's sample are rendered in RenderDoc as white-screen;

---

Tested on:

GPUs:

• Intel Arc A770
• AMD Radeon RX 6750 XT;

Apps:

• "Ray query" sample from SaschaWillems
• "Basic ray queries" sample from KhronosGroup (known issue)
• Quake II RTX (free on Steam) - set to use VK_KHR_ray_query instead of VK_KHR_ray_tracing_pipeline

  (options → graphics settings → ray tracing API → prefer VK_KHR_ray_query)

[baldurk]

This PR clashes with ongoing work - see #3271 - so I'm going to close it. You're free to keep this code locally on your branch, though note that soon it will likely conflict quite significantly.

In future if you're going to work on such a large feature like this I strongly recommend that you communicate first to check that there isn't any other work happening already that might clash, and that the changes you are making are in the right direction and desired. That prevents any wasted effort that happens from working on code changes only to find that they aren't something that is wanted upstream.

If you'd like to contribute to this functionality you might get in touch with @cmannett85-arm who's currently working on landing code.