Object3D: Ensure .localToWorld() uses the updated world matrix

[WestLangley]

... as in Object3D.getWorldPosition(), etc.

[Mugen87]

There is already a discussion about this topic, see #20220.

In this issue, there was no consensus about making the change proposed in this PR.

Although I favor the call of updateWorldMatrix(), we should not forget the update matrix computations in three.js are expensive since no caching system is in place. Besides, @donmccurdy raises concerns about always calling updateWorldMatrix() and proposed different solutions #20220 (comment).

[donmccurdy]

It's OK. I still think there's a challenge we're going to need to think about eventually on performance, but having different methods (.localToWorld, .getWorldPosition) perform differently will only confuse people further.

If there are specific performance ceilings we can measure and discuss, we'll work on that too.