[meta] Vulkan presentation on Nvidia Optimus/Prime

[kvark]

Trying to collect everything we know about this annoying blocker.
TL;DR: on Intel+Nvidia systems, under unknown circumstances, one of the physical devices is failing to either create a surface or present on it, despite Vulkan listing it as the first and specifying the ability to present.

Upstream:

• https://gitlab.freedesktop.org/mesa/mesa/-/issues/4688
• https://gitlab.freedesktop.org/mesa/mesa/-/issues/12212
• https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10430
• vkEnumeratePhysicalDevices should return the primary GPU first KhronosGroup/Vulkan-Loader#153

Issues:

• crashes on startup for PRIME enabled hardware thats configured to use the onboard nvidia not the intel #88
• Cube example fails on Ubuntu 20.10 with Nvidia graphics card enabled gfx-rs/wgpu-rs#673
• WL Vulkan apps are broken with PRIME NVIDIA/egl-wayland#72
• Fix broken Vulkan+Wayland apps with PRIME rpmfusion/nvidia-kmod#3

Mentions:

• Switch to a single GPU context in Blade zed-industries/zed#20853 (comment)

Affected user configurations:

DE	Nvidia	Intel	source	notes
X11	460.67	?	https://gitlab.freedesktop.org/mesa/mesa/-/issues/4688
X11	470.223.2.0	23.2.1	#88 (comment)
X11	1975239040	96477185	zed-industries/zed#8168 (comment)	Nvidia is first, but lacks "KHR_dynamic_rendering"
X11	470.239	?	zed-industries/zed#8168 (comment)
X11	550.127.5.0	23.3.4	zed-industries/zed#14225	Intel is default, shows blank screen but doesn't error
Wayland	525.105.17	?	NVIDIA/open-gpu-kernel-modules#317 (comment)
Wayland	530.41.03	?	mpv-player/mpv#11711 (comment)
Wayland?	550.78.0.0	24.0.6	zed-industries/zed#11475 (comment)
Wayland	550.54.14.0	N/A	zed-industries/zed#8168 (comment)	single-GPU system

Ideas:

• there appears to be a correlation with platforms. Users on X11 are unable to present with Intel (when Prime selects Nvidia), but users on Wayland are unable to present with Nvidia.