Reduced output spam from rapid property changes

[TheSofox]

Fixes #84499

Previously rapid changes in properties (dragging on colour picker, spinning through the spinner, etc.) would generate a huge amount of Output Log messages in a very short period of time. This would not only flood console, but eat up a lot of RAM.

This change means that the Property change messages use the same system that UndoRedo and History log uses: Identical changes made less than 800 milliseconds apart only give a single output message. Previously, messing around with the colour picker could give hundreds of messages, now it will only give a handful. Since it reuses the same system that , there's both minimal code change and it's consistent.

[KoBeWi]

Note that this change assumes that we use the callback only for editor log. Although it was always the case, so it's probably fine 🤔

[TheSofox]

Note that this change assumes that we use the callback only for editor log. Although it was always the case, so it's probably fine 🤔

If it's a sticking issue, we could add an "action_was_merged" argument to the callback function, pass the variable along and then make the conditional statement of whether to add a message or not inside the callback function ( void EditorLog::_undo_redo_cbk in editor_log.cpp)

[akien-mga]

Thanks!