When reading an array, it is only cleared right before new items are going to be added, instead of it being done before an attempt to read the value has been made.

`GameObject`, instead of comparing all options against each other, now saves the state of and compares individual ones, so the change data is more memory-efficient.

This way of tracking object changes also allows for proper undo/redo tracking with multiple remote users.

`GameObjectState` was renamed to `GameObjectChange`, since it does not always preserve all object options anymore.

TODO: Proper tilemap tile-change tracking

Previously, an assertion was used for performing this check, which was the cause of the crash. It wasn't taken into account performing undo/redo on a remotely-deleted object.

Additionally, the warning message now includes the class name of the object.

`TileMap` tile changes are now stored in pairs, containing a tile array index and old/new tile, which takes its place.

Allows for lighter storage in memory for undo/redo, as well as for lower-sized packets and proper remote tile undo/redo with editor remote level networking.

[ci skip]

[ci skip]