Node: Fix .getNodeType() if .construct() return some Node

[sunag]

Related issue: Fixes #26630

Description

.getNodeType() must be the same of Node returned from .construct() if any, so that the type references are correct.

[linbingquan]

@sunag I would like to ask a simple question, how do you locate or analyze this problem, I can not find any helpful information in the error message of the debugging panel, I tried to debug, but it did not work well. Maybe I'm not familiar with the WebGPURenderer module code.

I wonder if it is convenient for you to share your experience.

[sunag]

The error presented was from a WGSL generated a vec4f( vec3f(), vec3f() ), so I figured it was a compilation problem, TSL automatically converts the type differences, and I started to investigate if there was a specific Node with problem that AxesHelper was being used, then I noticed the Vertex Color, but the code was correct, it would certainly be a Node System issue.

three.js/examples/jsm/nodes/materials/NodeMaterial.js

Line 164 in 52c8584

colorNode = vec4( colorNode.xyz.mul( attribute( 'color' ) ), colorNode.a );

This was a global fix for Node System, it will certainly appear at some point or another.

When construct() returns a Node, some Nodes were using .getNodeType() to get the type of a child Node, and the data was not getting updated with the return of .construct(). I arrived at this conclusion debugging the line above, in the construct() and generate() processes.

I'm hopeful that after stabilizing the Node System we will create documentation explaining these processes better, mainly so that users can create their own Nodes or import from other 3d software.