zink and vulkan instance versioning issue
I recently went to fix some bug in lavapipe where it was exposing a 1.2 instance version when it should be only exposing 1.0 but zink broke when I did this.
I'm not 100% sure where the fault lies here.
Vulkan allows the loader to expose a 1.2 instance version when the underlying ICDs only expose a 1.0 instance version. However I'm not quite sure yet how the application should decide to use extensions vs core functionality for things like VK_KHR_get_physical_device_properties2. At the moment zink relies on the instance version, but this blows up when the loader is 1.2 but the ICD is only exposing 1.0