Expose desired_maximum_frame_latency through window creation

[Kanabenki]

Objective

• Closes Expose maximum_frame_latency from wgpu to Bevy users #12930.

Solution

• Add a corresponding optional field on Window and ExtractedWindow

---

Changelog

Added

• wgpu's desired_maximum_frame_latency is exposed through window creation. This can be used to override the default maximum number of queued frames on the GPU (currently 2).

Migration Guide

• The desired_maximum_frame_latency field must be added to instances of Window and ExtractedWindow where all fields are explicitly specified.

[james7132]

Shouldn't this change depending on if pipelined rendering is enabled as the initial issue suggests?

[Kanabenki]

I'll try to do some general latency benchmarking to see the impact of changing from 2 to 1 when pipelined rending is disabled. From some quick testing it seemed that this had a neutral to negative impact on the average frame rate when running some stress tests, but I didn't test latency yet and that's probably the main thing to check for.

[Elabajaba]

Just want to note that I was wrong about 2 being what we we're using previously (wgpu defaulted to 3 (triple buffering), but changed their default to 2 in the PR that added this setting), though we've been using 2 for bevy 0.13 so not really sure if it matters.

[alice-i-cecile]

I'm fine to defer changing the default for pipelined rendering to a follow-up, but I am curious about the results.

[Elabajaba]

Code looks good.

I did some unscientific latency benchmarking using presentmon's click to photon latency measurements, and 1 frame was quite a bit worse than 2 with pipelined rendering when I tested it with scene viewer (probably due to the lower framerate, or maybe inaccuracies in presentmon's latency measurements?)

[Kanabenki]

Sorry for getting back late, did some quick testing with pipelined rendering disabled to see if switching to one frame for that case might make sense, running on this scene I got way worse frame times (80 against 50 fps), and worse latency (40 against 50ms) using Presentmon.