Remove VoxelPrimitive.jitter option

[jjhembd]

The VoxelPrimitive.jitter option applies random shifts to the starting point for voxel ray-marching. This helped blur artifacts at the edges of voxels when using a constant step size.

After #11875, voxels use an optimum step size which fixes the artifacts. This makes the jitter unnecessary, and also effectively ignores the jitter after the first step.

This option should be removed. Since the voxel API is flagged experimental, we may not need a deprecation period.

[okrayum]

Hello @ggetz, Jason from JTC here and I would like to work on this issue, please.

[ggetz]

@okrayum Sounds good, thanks!

[okrayum]

Hello @ggetz I made a PR #12146 for this issue.
cleanup: Remove VoxelPrimitive.jitter option (#11913)

[okrayum]

I referenced 2 failing tests in the issues already known with those specs, however these are both different errors than what's listed in the existing issues

Chrome 128.0.0.0 (Windows 10): Executed 14263 of 14331 (2 FAILED) (skipped 68) (2 mins 35.598 secs / 2 mins 23.207 secs)
TOTAL: 2 FAILED, 14261 SUCCESS

1) picking in 3D
   Scene/GroundPolylinePrimitive
   Expected 'depth rectangle' to equal 'polyline on terrain'.
   at <Jasmine>
   at packages/engine/Specs/Scene/GroundPolylinePrimitiveSpec.js:821:27 <- Build/Specs/SpecList.js:178937:27
   at compare (Specs/addDefaultMatchers.js:387:13 <- Build/Specs/karma-main.js:355:13)
   at <Jasmine>

2) renders pnts with style and normals
   Scene/Model/Model3DTileContent pnts
   Expected 1 to be 0.
   at <Jasmine>
   at packages/engine/Specs/Scene/Model/Model3DTileContentSpec.js:919:29 <- Build/Specs/SpecList.js:253629:29
   at compare (Specs/addDefaultMatchers.js:314:13 <- Build/Specs/karma-main.js:296:13)
   at <Jasmine>
   Expected 1 to be 0.
   at <Jasmine>
   at packages/engine/Specs/Scene/Model/Model3DTileContentSpec.js:920:29 <- Build/Specs/SpecList.js:253630:29
   at compare (Specs/addDefaultMatchers.js:314:13 <- Build/Specs/karma-main.js:296:13)
   at <Jasmine>