Task list for VK_KHR_opacity_micromap release

Adds a new `VK_ACCELERATION_STRUCTURE_TYPE_OPACITY_MICROMAP_KHR` acceleration structure type that associates per-sub-triangle 1-bit or 2-bit opacity data with geometry in a bottom-level acceleration structure, enabling hardware-accelerated opacity testing during ray traversal without invoking any-hit shaders. A promotion of `VK_EXT_opacity_micromap` with significant API changes, see the proposal document for details.

The task list for the VK_KHR_opacity_micromap release is:

- [x] Vulkan Specification: https://docs.vulkan.org/refpages/latest/refpages/source/VK_KHR_opacity_micromap.html
- [x] SPIRV specification: https://github.khronos.org/SPIRV-Registry/extensions/EXT/SPV_EXT_opacity_micromap.html
- [x] SPIRV Headers: https://github.com/KhronosGroup/SPIRV-Headers/pull/292
- [x] SPIRV tools released: https://github.com/KhronosGroup/SPIRV-Tools/pull/6670
- [x] GLSL extensions:
- [x] https://github.com/KhronosGroup/GLSL/blob/main/extensions/ext/GLSL_EXT_opacity_micromap.txt
- [x] https://github.com/KhronosGroup/GLSL/blob/main/extensions/ext/GLSL_EXT_opacity_micromap_ray_query_mode.txt
- [x] Glslang implementation: https://github.com/KhronosGroup/glslang/pull/4332
- [x] Conformance tests released: https://github.com/KhronosGroup/VK-GL-CTS/commit/cd8f546bd45284def19ecc6ec6fd3faea3aaaf4e
- [ ] Validation layer:
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12292
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12560
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12563
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12595
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12607
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/12685

As each component is made public, the task will be checked off. When all tasks have been completed this issue will be closed and the extension will be fully released.

Review the unchecked Validation layer item and its referenced Vulkan-ValidationLayers pull requests first. Compare their status with the release checklist; the issue is complete when the validation-layer work is public and every task is checked off.

Written by the indexing model from the issue text.