Bump 3d tiles renderer to 0.4.4 and three.js to 0.170.0

[Desplandis]

Description

This PR bumps 3d-tiles-renderer from 0.3.39 to 0.4.4 and three.js from 0.168.0 to 0.170.0.

Changes in three

r169

See changelog and migration guide.

There is no changes impacting iTowns.

A list of interesting changes (feel free to extend it):

• Raycaster
  • Add barycoord to intersection result, make attribution interpolation more convenient. Raycaster: Add barycoord to intersection result, make attribution interpolation more convenient. mrdoob/three.js#29340 (@gkjohnson). In feat(3d-tiles): support picking of metadata #2493, we manually calculate the barycoord from the intersection result, we may not need it anymore.
• WebGLRenderer
  • Merge update ranges before issuing updates to the GPU. WebGLRenderer: Merge update ranges before issuing updates to the GPU. mrdoob/three.js#29189 (@HunterLarco)
  • Fix feedback loop with RTT read pixels async. WebGLRenderer: Fix feedback loop with RTT read pixels async mrdoob/three.js#29320 (@gkjohnson). For picking metadata in iTowns.
  • Reduce readRenderTargetPixelsAsync() latency. WebGLRenderer: reduce ReadRenderTargetPixelsAsync latency mrdoob/three.js#29339 (@aardgoose). For picking metadata in iTowns.

r170

See changelog and migration guide.

A list of interesting changes (feel free to extend it):

• BatchedMesh: different changes used internally by 3d-tiles-renderer (see BatchedMeshPlugin below)
• WebGLTextures
  • Ensure depth texture properties are deleted. WebGLTextures: Ensure depth texture properties are deleted. mrdoob/three.js#29697 (@Mugen87)

Changes in 3d-tiles-renderer

There is some changes impacting iTowns, especially for plugins. I disabled some eslint check on imports since it does not support package.json imports... (see import-js/eslint-plugin-import#1868). It seems eslint-import-resolver-typescript works but decided to go for disabling this warning for now.

Added

• load-error events when model, tile set, and API token requests fail to fetch or parse. To use internally in iTowns and provide a way to the user to access this event.
• PNTSLoader: Add support for normals, quantized normals.
• TilesRenderer: Support for 3DTILES_ELLIPSOID extension.
• TilesRenderer: added "loadProgress" field.
• BatchedMeshPlugin plugin: Plugin: BatchedMeshPlugin NASA-AMMOS/3DTilesRendererJS#628. I think we should examine the performance gains in using BatchedMesh for 3D Tiles rendering.

[AnthonyGlt]

There is a breaking change for the WEBXR example, probably this one
#2473

BUT I'm currently working on a refactoring of the webxr.

Should we put it in deprecated for now ?

[Desplandis]

@AnthonyGlt Depends on whether or not we considered the WebXR example as ready to production or not.

[AnthonyGlt]

There is already a webxr example available (view_3d_map_webxr) , I'm just saying that with this bump, it wouldn't work anymore.
For now, we should, at least, remove the access to this example from the config.json, until incoming refactoring. I don't think that we should hot fix it because of this refactoring.
IF we rather hot fix it, I've gave a solution in the issue mentioned above.
WDYT ?

Either way, some changes should be made in this file
to fix it or to link to the issue, so users will know that it's temporarily broken and how to bypass the bug

[Desplandis]

Okay, I added the quickfix in the example as suggested in your issue, that should be good enough. =)