NodeMaterial: Introduce .geometryNode and jelly example

[sunag]

Related issue: #29547

Description

The goal is to have a dedicated API for dealing with geometry, whether during a single frame or the every frame that the object is rendered. This also simplifies the integration of modifications with new objects since all the user needs to define is typically material.geometryNode = myGeometryNode() like the example bellow.

// With the 'material.geometryNode' there is no need to worry about the 'renderer.compute( node )'.

const material = new THREE.MeshNormalNodeMaterial();
material.geometryNode = jelly();

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	688.13 170.5	688.13 170.5	+0 B +0 B
WebGPU	807.88 217.63	808.1 217.67	+213 B +38 B
WebGPU Nodes	807.39 217.49	807.61 217.53	+213 B +38 B

🌳 Bundle size after tree-shaking

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

	Before	After	Diff
WebGL	462.85 111.78	462.85 111.78	+0 B +0 B
WebGPU	536.32 144.76	536.53 144.8	+213 B +40 B
WebGPU Nodes	492.4 134.49	492.61 134.53	+213 B +42 B

[mrdoob]

FYI @boytchev

[boytchev]

Thanks for the head-up. This looks very promising for the type of things that I use TSL for. I still had to fully understand the jelly example in webgpu_compute_geometry.html. I have some why-questions, but I will first try to answer them by myself. And ... I feel sorry for Lee Perry Smith - his head appears to be the most tortured model in the world.