Implement DXGI swapchain for vulkan

[cwfitzgerald]

We have a long history of swapchain related issues on vulkan windows.

• Don't use VkSurface and EglSurface on supported platforms #8100
• FIFO present modes lead to a long wait for semaphores on Vulkan #8310
• Increased input-to-screen latency on vulkan #6932
• Vulkan color space is different when rendering to swap chain (sRGB) #4842
• Window resizing lags with white rectangles on Windows #5374
• Screen flickering on Nvidia Optimus #3452
• Portable window transparency: alpha mode? #3486 .

And apis that are blocked on vulkan swapchains not having the extensions needed to do a good job of latency reduction.

• Extended Presentation API Investigation #2869

All of these problems do not exist on DX12 where we're using a DXGI swapchain.

Previously we've discussed switching the default backend to DX12 on windows (#2719) to help eliminate these problems, but with the shader story being what it is, that's not really a way forward.

The next best thing is to do interop with a DXGI swapchain on windows so that we get the tools that the DXGI swapchain provides. These include

• FrameLatencyWaitableObject and sane latency controls
• DXGI frame statistics
• Much better frame pacing

I'm very motivated to get this in, so let me lay out my plan for landing this and rolling it out.

• Factor out swapchain to abstracted interface #8356
• Implement DXGI Swapchain on Vulkan #8388
• Ask people to test using the new swapchain, make sure it's solid.
• Once confident and still early in the release cycle, turn it on by default so more people can test with it.
• Before release when getting people to test us, make sure they test the swapchain on windows.
• If solid, release with it by default, if not go a version without it by default for more testing and bug fixes.

[cwfitzgerald]

Discussed at today's wgpu matainers meeting, going to paste in the summary of the problem and solution from the notes.

• CF: When running on Vulkan, on new drivers, on Windows, when your application is running faster than the monitor, you’re relying on the swapchain to limit your pace to the speed of the monitor. The resulting limiting is extremely inconsistent, causing stuttering. This only happens if the drivers are implicitly using a D3D swapchain to implement the Vulkan swapchain.
• The solution is to have wgpu, directly, use a D3D swapchain instead of a Vulkan swapchain. This means that the wgpu-hal vulkan backend will actually be using a D3D swapchain on Windows. This also gets us other D3D swapchain features that Vulkan’s swapchain lacks. The plan is to make this the default, since the behavior is so much better.
• I’m taking an aggressive stance on asking for expeditious PRs for this because it’s a very bad bug that affects a lot of people.
  • We’re also at a point in the release cycle where I want people to really test things before we expose things via release.
  • The biggest risk seems to be bugs written by Connor, not the technique itself.