Vulkan: Update all components to Vulkan SDK 1.4.335.0

[akien-mga]

Needs to be tested on all platforms where we support Vulkan, but also D3D12 and Metal for SPIR-V.
Our last sync was almost 2 years ago so this is long overdue, and thus would be good to include in 4.6.

Updated:

• vulkan headers
• volk
• glslang
• spirv-headers
• spirv-cross
• spirv-reflect
• vk_mem_alloc 3.3.0

TODO:

• SPIRV-Reflect not updated yet as they implemented support for specialization constants which conflicts with our patches, so this needs some work to use the new upstream API if suitable.
  @DarioSamo Would you be able to take a look at doing the SPIRV-Reflect update as a PR/direct push to my branch?
  Edit: Done, thanks Darío!
• VulkanMemoryAllocator not updated as it's not versioned together with the SDK, and it often requires more work.
  Could be done in a separate PR if that sounds reasonable, or in this PR if we risk having issues by sticking to an older version.
  Edit: Done, we can remove it if it causes issues.
• Update MoltenVK for official builds. WIP in Update MoltenVK to 1.4.1 (for use with SDK 1.4.335 and later) moltenvk-osxcross#5.
  Edit: Done with macOS/iOS: Update MoltenVK to 1.4.1 for Vulkan SDK 1.4.335.0 godot-build-scripts#143.

Supersedes #107773.

[akien-mga]

I'm tired of having to manually delete .orig and .rej files generated by GNU patch (one had managed to slip through in this PR at first), so I'm gitignoring them. I don't expect it to conflict with legit file extensions we'd want to version.

[akien-mga]

SPIRV-Reflect now also updated to 1.4.335.0 with the upstream specialization constant support thanks to @DarioSamo!

[akien-mga]

I added the VulkanMemoryAllocator update to 3.3.0 in the end, so we can test everything at once.
If you run into issues testing this PR, please try a local revert of the VMA update to see if that solves it.

[Calinou]

Tested locally on several demo projects (Linux + NVIDIA), this causes reflection probe rendering to break on the 3D platformer demo. It appears as pure black and this error is printed every time a reflection probe is rendered:

ERROR: This render pipeline requires (4) bytes of push constant data, supplied: (16)
   at: draw_list_set_push_constant (./servers/rendering/rendering_device.cpp:4951)
ERROR: The shader in this pipeline requires a push constant to be set before drawing, but it's not present.
   at: draw_list_draw (./servers/rendering/rendering_device.cpp:4984)

This occurs on both Forward+ and Mobile. The issue happens with the first commit only (no VMA update), or when both commits are applied.

[akien-mga]

Added a fix by @DarioSamo that should solve the issues @Calinou documented.

There might be more similar cases that will warrant extensive testing, so we decided to postpone this to 4.7. It should still be tested well (can be done now) and merged early in the dev phase, so we have time to be confident that it doesn't create regressions before 4.7 beta.

[Calinou]

Works great now 🙂

I've also tested it on several other demos like the TPS demo, as well as baking lightmaps.

[AR-DEV-1]

Works as expected on Linux (Zorin OS 18) when using the Forward+/Mobile renderers (Vulkan).

[blueskythlikesclouds]

What happened to the push constant padding changes? Are they not required now?

[akien-mga]

I amended them in the commit, so they should be there.

Edit: No I messed up, I forgot to pull in my local branch before rebasing. I'll fix it up.

[akien-mga]

I restored the VMA update and the structure padding fix.

[bruvzg]

Tested on macOS and iOS, with aforementioned octmap_downsampler_raster.glsl padding patch applied it seems to be working fine.

[blueskythlikesclouds]

Looks good to me!

A concern I have is that the glslang update may affect people using RD with GLSL in their games if they don't have proper padding in their push constants. The error is easy to fix and the log is pretty clear, though.

[Repiteo]

Thanks!