Inconsistent Behavior: insertMany Does Not Trigger Mutation Events in Editor.js

The question.

In Editor.js, various block operations such as delete, add, and move trigger the onChange event, allowing developers to handle mutations in a consistent manner. However, when using insertMany to add multiple blocks at once, the onChange event is not triggered.

This inconsistency in behavior can lead to unexpected issues, particularly in applications that rely on onChange for synchronization or state updates. For instance, developers might expect that inserting multiple blocks via insertMany would behave similarly to adding blocks one at a time, but this is not currently the case.

Would it be possible to align the behavior of insertMany with other block operations by ensuring that it triggers the onChange event? This would improve consistency and make the API more predictable for developers.

Why and how the question has come up.
Since insertMany did not fire `onChange`.
Using `@editorjs/editorjs@2.30.7`