`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`

As discovered in #7126 this might be either a regression in Chrome 128 or a bug in plotly.js & stackgl dependencies.
cc: @birkskyum 

Error message: 
```
TypeError: Failed to execute 'uniformMatrix4fv' on 'WebGLRenderingContext': The provided float value is non-finite.
```