Renaming material inserts two entries to undo stack despite it being done inside transaction

When renaming materials, objectName and id change are both done inside same transaction, but for some reason both are generated as separate undo steps.

Looks like the culprit is setIdWithRefactoring, which seems to bypass the transaction and directly commit the changes it does. However, this method is also used elsewhere inside transactions without causing duplicate undo stack items.