New package: VulkanMemoryAllocator-3.4.0

[Rutpiv]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for my native architecture (x86_64)
• I built this PR locally for these architectures using specific masterdirs:
  • x86_64-musl
  • i686
• I built this PR locally for these architectures (crossbuilds):
  • aarch64
  • aarch64-musl
  • armv7l
  • armv7l-musl
  • armv6l
  • armv6l-musl

[Rutpiv]

Follow-up to #61152, where I mentioned I would keep going with the SDK components Void is still missing. This is the first of them.

VulkanMemoryAllocator is an official Vulkan SDK component and the last header-only one still missing here, same shape as Vulkan-Headers and SPIRV-Headers.

Upstream exports an INTERFACE target, so the SONAME scanner cannot see the Vulkan headers and depends="Vulkan-Headers" is explicit. VMA_ENABLE_INSTALL already defaults to on for a top-level build, so the only configure argument is -DVMA_BUILD_DOCUMENTATION=ON, split into VulkanMemoryAllocator-doc. Upstream ships HAVE_DOT = NO, so graphviz is not pulled in.

Tested from an out of tree CMake project with find_package(VulkanMemoryAllocator CONFIG REQUIRED) linking GPUOpen::VulkanMemoryAllocator. The config is INTERFACE only and does not pull Vulkan, so the consumer needs its own find_package(Vulkan). vmaCreateAllocator and vmaCreateBuffer ran against RADV and lavapipe with identical results.