Fix compound colliders

[LeXXik]

Fixes #6976

The issue was that when we loop over compounds during physics update, we go over all nodes of the compound entity:

engine/src/framework/components/collision/component.js

Line 694 in 91148f0

entity.forEach(this.system.implementations.compound._updateEachDescendantTransform, entity);

Since we use entity.forEach, that includes the parent itself, which adds parent compound shape as a child to itself. When 2 such compounds collide, the bullet physics locks in a loop, causing max stack exception.

While at it, also changed the frequency of the children shapes transform updates. Instead of removing and adding them every frame if parent moved, they are now updated only when their own transforms changed or they are recreated.

I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

[willeastcott]

Hey @Maksims, this looks ok to me. But I think you wrote the original support for compound collision shapes, right? Would you be able to cast your eye over this too please?

[Maksims]

I think it was caused by my assumption that forEach would not include self into the loop. It has been 5 years since.
If tested and works well, good fix!

[LeXXik]

@willeastcott this should be good for v1 as well.

[willeastcott]

@LeXXik I have just cherry-picked to main_v1.