Restore restarted watchdog editor with current react state

[Mati365]

Suggested merge commit message (convention)

Fix: Prevent potential crashes of useMultiRootEditor during the initialization phase when setting the new state of the multi-root editor with an attached watchdog. Closes #542

---

Additional information

It appears that some of our tests are causing random restarts of the editor. An example of such a restart might occur when setting some data while the component has not fully rendered the entire CKEditor, and the semaphore begins destroying it while running in the watchdog context.

This PR resets the reinitialized editor data to the one defined in the React state (data is defined in the upper scope). This change seems to make our tests more stable and should be harmless.

[coveralls]

Pull Request Test Coverage Report for Build e60bbb33-6ee8-42a4-9a3f-558ebc50367c

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 99f1a8b3-7db2-4b7a-b3cb-6130df28e2ca:	0.0%
Covered Lines:	582
Relevant Lines:	582

---

💛 - Coveralls

[f1ames]

Should we have a dedicated test for that? Now we have one which sometimes fails due to previous behavior (but it may not), so this specific logic is not really covered 🤔

[Mati365]

@f1ames I don't think so, simulating this is too difficult, and it's that kind of behavior that often changes with React implementation changes.

[f1ames]

@f1ames I don't think so, simulating this is too difficult, and it's that kind of behavior that often changes with React implementation changes.

Ok, I agree. LGTM then 👍