WebGPURenderer: Introduce compileComputeAsync()

[RenaudRohlinger]

Description
Same logic as compileAsync(), compileComputeAsync() Prevent freeze in runtime.

Example usage:

await renderer.init()
await renderer.compileComputeAsync([ clearGridKernel, p2g1Kernel, p2g2Kernel, updateGridKernel, g2pKernel ])
await renderer.compileAsync(scene, camera)
renderer.setAnimationLoop( render );

Before:

After:

Also added a basic onProgress callback for both compile and compileCompute:

This contribution is funded by Utsubo && Three.js Blocks

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	355.17 84.44	355.17 84.44	+0 B +0 B
WebGPU	618.17 171.68	620.04 172.12	+1.87 kB +443 B
WebGPU Nodes	616.78 171.43	618.64 171.88	+1.87 kB +444 B

🌳 Bundle size after tree-shaking

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

	Before	After	Diff
WebGL	487.34 119.31	487.34 119.31	+0 B +0 B
WebGPU	688.81 187.1	690.67 187.52	+1.87 kB +417 B
WebGPU Nodes	638.65 174.3	640.52 174.73	+1.87 kB +425 B

[sunag]

I think this calculation should be done on the user side. Maybe we could use ProgressEvent() to follow the pattern used in Loader?