[Rob-Hughes-Arm]

Problem

The shared creation paths have two failure-handling gaps:

• VkInstanceCreateInfo::pApplicationInfo may legally be null, but the framework dereferences it when reading the API version and when updating the safe copy for version promotion. An explicit apiVersion of zero is also treated as version 0.0 instead of Vulkan 1.0.
• After the underlying vkCreateDevice call succeeds, constructing the layer's Device wrapper or publishing it in the global store can throw. Without rollback, the underlying device remains alive without a usable layer wrapper, and the output handle is left populated.

Changes

• Treat absent application info and API version zero as Vulkan 1.0.
• Allocate application info in the owned safe copy before version promotion, leaving the caller's input unchanged.
• Guard device-wrapper construction and publication. On failure, release the tracking lock, clean up remaining local wrapper state, destroy the underlying device with the original allocator, and clear the output handle.
• Return VK_ERROR_OUT_OF_HOST_MEMORY for allocation failures and VK_ERROR_INITIALIZATION_FAILED for other construction/publication exceptions.

Successful device publication is unchanged. Driver destruction remains outside the tracking lock.