Update propogate_transforms to only visit the transforms of entities that have changed

[BenjaminBrienen]

As far as I know yes, the transform propagation algorithm hasn't been changed since posting this. In order to alleviate the performance concerns we'd need two changes:

1. Update propogate_transforms to only visit the transforms of entities that have changed. Currently we visit the entire hierarchy on every run of the system which is very inefficient (this is sub-optimal regardless of whether we update transforms in FixedUpdate, but this issue would exacerbate it)
2. We'd need a way of sharing change ticks between multiple instances of propogate_transforms. Currently, if you were to add propogate_transforms to the schedule multiple times, each instance of the system would have its own change ticks, which means each instance would redundantly propagate transforms for the same entities/components

Originally posted by @JoJoJet in #7836 (comment)

item 2 can be a follow-up after this issue is handled

[joseph-gio]

Reposting my comment from the original issue for visibility (pun not intended)

See also #9497, which updated the visibility propagation algorithm to only visit entities that were changed. That exact approach may not be ideal for transforms though, since it can result in redundant propagations for a single entity within the same frame. For visibility, we figured that the tradeoff was worth it since propagating visibility is relatively cheap, and the cost of visiting the entire hierarchy tends to be more expensive than propagating changes entities. Transform propagation is computationally more expensive so it's not clear if that same tradeoff would be worth it.

[NthTensor]

Yeah, the naive approach used in #9497 is going to cause problems for transform propagation. It's not just non-ideal to propagate multiple times, I believe it would be potential UB. Since transform propagation is highly parallel, double propagation could result in conflicting mutable access.

The method used by big_space should be adapted here. I've been planning to do this for a while, and will probably do so shortly after cart's relations stuff merges.