zink: add VK_STRUCTURE_TYPE_WSI_MEMORY_ALLOCATE_INFO_MESA for WSI allocations
Since Zink doesn't use swapchains to create presentable images, drivers lose the capacity to identify memory allocations for them, which is a problem when the underlying platform has special requirements for these, such as needing to allocate them on a particular device. Including this struct in the pNext chain, which is the same thing that the Mesa Vulkan WSI code does when allocating memory for swapchain images, gives drivers a chance to identify and handle these memory allocations properly.
@kusma: this, together with a few MRs that I have waiting for review for v3dv (VK_KHR_maintenance1 and timestamp queries) gets things working with Zink for us.