Vulkan-Headers and Vulkan-Loader 1.4.309

[Bruce Dubbs]

New point version.

Appears to be a coordinated release with SPIRV packages.

[Douglas R. Reno]

Vulkan-Headers

Update for Vulkan-Docs 1.4.305 
Update for Vulkan-Docs 1.4.306 
Update for Vulkan-Docs 1.4.307 
cmake: Update minimum version to 3.22.1
  Matches Vulkan Validation Layers and SPIRV-Tools.
Update for Vulkan-Docs 1.4.309 

[Douglas R. Reno]

Vulkan-Loader

build(deps): bump github/codeql-action from 3.27.9 to 3.28.0 
Better document the header version VK_DRIVER_FILES was added 
Rename loader_platform_* to test_platform_*
  This prevents conflicts with the loaders and tests platform abstractions.
Use GoogleTest as static library 
Allow tests to directly call loader internal functions
  This allows the fuzz tests to faithfully recreate the calling environment
  of OSS-Fuzz, meaning reproduction of failing fuzz tests can be done in the
  repo for regression testing.
  The implementation of this requires exporting several functions that the
  fuzz tests need which is done with a new macro that is only active when
  a specific compiler definition is set, which the build does when testing
  is active.
Always memset newly reallocated memory
  Fuzz testing found a case where memory was left uninitialized after
  calling loader_realloc, causing a crash due to reading of that memory.
  The fix is to *always* memset newly reallocated memory, since a value of
  zero is a good default value, especially if that memory is for a list.
  This commit removes the redundant memsets, since realloc now has the
  responsibility to initialize memory.
Include fuzz test which needs realloc memsetting 
build(deps): bump github/codeql-action from 3.28.0 to 3.28.1 
Make emulate_VK_EXT_surface_maintenance1 more comply to vk spec
  The emulation function does not comply with specifications.
  The spec asks ```The implementation must include the present mode
  passed to VkSurfacePresentModeEXT in pPresentModes,
  unless presentModeCount is zero.``` But now the implementation here
  will always include the present mode regardless of whether
  presentModeCount is zero.
  According to spec ```If the value of presentModeCount is less than
  the number of compatible present modes that are supported, at most
  presentModeCount values will be written to pPresentModes.``` When
  presentModeCount is 0, at most 0 values will be written to
  pPresentModes, in other words the implementation should do nothing
  in this situation.
  This commit fixed the above issue.
Fix log message in vkGetPhysicalDeviceSurfaceFormatsKHR 
Support VK_GOOGLE_surfaceless_query
  Requires bypassing the logic which dereferences VkSurfaceKHR in
  vkGetPhysicalDeviceSurfaceFormatsKHR and
  vkGetPhysicalDeviceSurfacePresentModesKHR. This should have been done
  closer to the release of VK_GOOGLE_surfaceless_query, but because that
  extension was meant for Android, which isn't supported by this loader,
  it was not done. That said, SwiftShader can support the extension, so
  support is now being added in this commit.
Revert "Remove unused VkIcdSurface struct members"
  This reverts commit 55bd9d6.
  The libMali.so driver still uses the older method of surface creation,
  so the struct members are still actually 'used'.
Better document VkIcdSurface ABI in wsi.h 
build: Update to header 1.4.305 
build: Update to header 1.4.306 
build(deps): bump github/codeql-action from 3.28.1 to 3.28.5
Add NULL checks for VkDeviceCreateInfo ppEnabledExtensionNames 
build: Update to header 1.4.307 
build(deps): bump github/codeql-action from 3.28.5 to 3.28.8 
Silence warnings for wrong manifest type
  If the loader happens upon a layer/ICD manifest while searching for manifests
  of the opposite type, do not emit warnings. These are spurious and only cause
  users to think something is wrong with the installation when it is actually
  fine.
cmake: Update minimum version to 3.22.1
  Matches Vulkan Validation Layers and SPIRV-Tools.
Allow settings with only debug logging to work
  Changes the logic of the loader settings file to allow settings files which
  just the stderr_log. This means settings that do not with to alter the layers
  can be achieved.
Prepend [Vulkan Loader] to stderr log output
  This makes it clear *who* is creating log messages, which wasn't as clear
  before.
  This commit refactors the logging code to be easier to understand.
Update docs to reflect changes in log output 
build: Update to header 1.4.309 

[Douglas R. Reno]

Fixed at 5600f695123c69ef6c6d261cc5f51521b387d03f