WebGPURenderer: Handle Device Lost Event

[RenaudRohlinger]

Description
Handle device/context Lost Event on both backends of the WebGPURenderer.

By default a formatted error will appear like so:

And just like in the WebGLRenderer, both loop will throw an early return.

Also added a way to easily handle the error for the developer:

renderer.onDeviceLost = ( info ) => console.log( 'Device Lost', info );

Even better, unlike WebGL, we could even gracefully restart the app/device in WebGPU:

renderer.onDeviceLost = ( _info ) => await renderer.init()

This contribution is funded by Utsubo

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	691.67 171.43	691.67 171.43	+0 B +0 B
WebGPU	820.87 221.46	821.69 221.79	+816 B +325 B
WebGPU Nodes	820.38 221.33	821.2 221.66	+816 B +328 B

🌳 Bundle size after tree-shaking

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

	Before	After	Diff
WebGL	463.82 112.17	463.82 112.17	+0 B +0 B
WebGPU	541.7 146.38	542.52 146.73	+816 B +343 B
WebGPU Nodes	497.7 136.21	498.52 136.55	+816 B +343 B

[Makio64]

@RenaudRohlinger thanks for this PR !

Can you confirm this part renderer.onDeviceLost = ( _info ) => await renderer.init() is only to call when _info.api =='WebGPU'

Also I guess it also needs to restart all the engine ( add back all items, restore all state etc.. ) right or can I use the previous texture / scene / material etc.. ?

Final question do you have an easy way to test the context lost ? :)

Thanks again !