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.34 84.47	355.34 84.47	+0 B +0 B
WebGPU	617.86 171.37	619.87 171.83	+2.01 kB +458 B
WebGPU Nodes	616.46 171.13	618.47 171.58	+2.01 kB +459 B

🌳 Bundle size after tree-shaking

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

	Before	After	Diff
WebGL	487.5 119.33	487.5 119.33	+0 B +0 B
WebGPU	689.3 187.14	691.31 187.6	+2.01 kB +454 B
WebGPU Nodes	639.15 174.35	641.16 174.81	+2.01 kB +453 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?

[RenaudRohlinger]

Updated the PR with the ProgressEvent()pattern!