Heightmap does not excute use when inserted in standardmaterial3D of a mesh

Nobody has claimed this yet.

### Tested versions

v4.2.1.stable.official [b09f793f5]
it also does not wok on v4.1.2

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - GLES3 (Compatibility) - GeForce GT 720M () - Intel(R) Core(TM) i7-4712MQ CPU @ 2.30GHz (8 Threads)

### Issue description

Heightmap does not excute use when inserted in standardmaterial3D of a mesh.

The heightmap was expected to be shown on the mesh after height was enabled and the heightmap inserted the a standardmaterial3D.

During the test triplanar was disabled and normal map function works fine. All scale of the height map and UV1 was changed but not thing changed for the height map.

This was tested on CSGmesh3D, Meshinstant3D and imported blender file with .blend

The 2 heightmap were tested, one was created using material maker export to godot format, the other was a noise texture from fastnoise within godot.

### Steps to reproduce

1. create new CSGmesh3D
2. create new plane mesh in property tab
3. create new StandardMaterial3D in material option
4. click the new material and enable height map
5. insert texture for height map by noise texture fastnoise or sample texture from computer

### Minimal reproduction project (MRP)

N/A

Start by reproducing the report with a CSGMesh3D or MeshInstance3D, a plane mesh, and a StandardMaterial3D using the listed heightmap steps. Check whether the heightmap appears with triplanar disabled and compare the behavior of the two tested textures. Done means the heightmap visibly affects the mesh in the reported Godot versions or the failure is narrowed to a documented engine limitation.

Written by the indexing model from the issue text.