Examples: Add webgpu_multiple_elements

[sunag]

Related issue: #27628

Description

Add webgpu_multiple_elements for WebGPURenderer and update the scissor limits if it is misconfigured making the example executable.

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	338.91 79.1	338.91 79.1	+0 B +0 B
WebGPU	577.78 159.15	578.02 159.2	+234 B +50 B
WebGPU Nodes	576.39 158.91	576.63 158.96	+234 B +51 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

	Before	After	Diff
WebGL	470.7 113.91	470.7 113.91	+0 B +0 B
WebGPU	648.33 175.2	648.56 175.25	+234 B +52 B
WebGPU Nodes	602.42 164.32	602.66 164.38	+234 B +51 B

[Mugen87]

I've done a bit more testing on dev and noticed that webgpu_multiple_elements reports warnings when used with a high resolution screen. This also happens on prod so the issue has not been introduced in the current sprint. On a 5K display, the following WebGPU warning is reported:

Viewport width (8468.000000) exceeds the maximum (8192). This adapter supports a higher maxTextureDimension2D of 16384, which can be specified in requiredLimits when calling requestDevice(). Limits differ by hardware, so always check the adapter limits prior to requesting a higher limit.
While encoding [RenderPassEncoder (unlabeled)].SetViewport(0.000000, 0.000000, 8468.000000, 4812.000000, 0.000000, 1.000000).
While finishing [CommandEncoder "renderContext_1"].

A viewport width of 8468 seems strange. Maybe a bug?

Side note: When reducing the size of the browser window, the warnings eventually disappear. Besides, the WebGL backend seems fine.

[sunag]

On a 5K display, the following WebGPU warning is reported:
A viewport width of 8468 seems strange. Maybe a bug?

Could your pixel ratio be greater than 1?

[Mugen87]

Yes, the pixel ratio is 2.