WGPU breaks on missing maxInterStageShaderComponents

[ErichDonGubler]

Recently, GPUSupportedLimits.maxInterStageShaderComponents was removed from the WebGPU spec. Firefox Nightly has changed to follow the spec's removal, but WGPU needed to change its code to not break (see gfx-rs/wgpu#6290 (comment) for work tracked on this).

When this happens in Firefox Nightly, an error with the following message is emitted in the console log, with the screen remaining black and the app unresponsive: Could not get WebGPU device: requestDevice: Limit 'maxInterStageShaderComponents' not recognized.

[ErichDonGubler]

The fix should be to Just™ upgrade the version of WGPU being consumed; I released v23 today, and that is what needs to be consumed. I don't know how this release propagates to C++ code (CC @cwfitzgerald), but I presume there is further work to do in wgpu-native before that Rust release is consumable by C++.

[sava41]

My hands are tied on the browser version of the app to whatever spec of WebGPU is used in Emscripten as it maps the c header api to the corresponding javascript functions. I tried updating to the latest emscripten version yesterday and that didn't fix the error message.