Unify texture loading and map property fixes

[mrxz]

Description:
Preparation work for #5449. Both utils.materials.updateMap and utils.materials.updateDistortionMap are used for setting texture maps. These methods had similar, but slightly different implementations. This PR unifies them by letting updateDistortionMap call updateMapMaterialFromData.

Removing these maps or changing texture properties are now also correctly handle. Before only the diffuse map could be removed when changing the map properties of the standard and phong shader. In case texture properties are changed that require a texture update, the needsUpdate flag is now also set. Note: textures are still shared based on their initial properties, this will be addressed in upcoming PRs.

Changes proposed:

• Use updateMapMaterialFromData in updateDistortionMap aligning it with updateMap
• Always call texture map update methods to allow removing textures (standard and phong shaders)
• Let setTextureProperties set needsUpdate on the texture when a property changes that requires it
• Add unit tests for testing unsetting maps and changing texture property requiring needsUpdate

[dmarcos]

This guards no longer needed?

[mrxz]

The guards prevented these textures from being removed. Similar to how the main (diffuse) map is handled, the underlying implementation of updateMapMaterialFromData checks if the texture is added, changed or removed, or if only the texture properties are updated.

[dmarcos]

guard no longer needed?

[mrxz]

The guard actually prevented offset from being set back to 0/0 after being set to something else. On top of that, changing the offset doesn't require a texture update, so there's nothing gained by skipping this.

[dmarcos]

checks no needed?

[mrxz]

Same as for standard.js

[dmarcos]

remove because of redundant?

[mrxz]

Indeed, this is in the init method, which is followed by update which also calls updateMap. Both flat and standard let the update handle this and phong was the odd one out.

[dmarcos]

Thanks!