fix(Texture): Prevent GL_INVALID_OPERATION when updating texture data

[PaulHax]

TODO

• I think we need account for datatype changes, among other tings =/

Prevent GL_INVALID_OPERATION when updating texture data in WebGL2

I would think this warning has been disccused before but could not find an issue regarding this...

Context

WebGL2 textures created with texStorage2D are immutable, causing browser console warnings:

GL_INVALID_OPERATION: glTexStorage2D: Texture is immutable.

This occurs when texture.modified() triggers recreation of existing textures, such as when updating video textures or other dynamic content. The warning appears because vtk.js attempts to call texStorage2D again on already-immutable textures.

Console log showing the error pattern:

• Initial texture creation: texStorage2D + texSubImage2D (works)
• Texture update: texture.modified() → attempts texStorage2D again (fails)

Want this to update a texture with a video stream.

Results

Before: Browser console shows GL_INVALID_OPERATION warnings on every texture update

After: Clean texture updates without any WebGL errors

The texture data still updates correctly in both cases, but the warnings are eliminated.

Changes

• Added: update2DFromRaw() method that uses texSubImage2D for data-only updates
• Modified: render() method to detect when only texture data changes (same dimensions/components)

API additions:

• publicAPI.update2DFromRaw({ data, dataType, flip }) - Updates existing texture data without recreation

• Documentation and TypeScript definitions were updated to match those changes

PR and Code Checklist

• semantic-release commit messages
• Run npm run reformat to have correctly formatted code

Testing

• This change adds or fixes unit tests
• Tested environment:
  • vtk.js: latest master
  • OS: Linux
  • Browser: Chrome WebGL2

Test coverage:

• Unit test verifies no GL_INVALID_OPERATION errors during texture updates

[floryst]

@sankhesh just an FYI (low priority)