fix: Update diffDOM to the latest version

[petrklus]

Description

Work in progress on #7460.

Upgrading diffDOM seems to resolve the issue, however, is not compatible with UglifyJS.

Related resources

The issue seems to be related to variable naming in diffDOM:

I belive it is due to the variable called node:

https://github.com/fiduswriter/diffDOM/blob/v4.2.8/src/diffDOM/dom/fromVirtual.js#L2

Which UglifyJS does not like. I am seeking help with getting this fix across the finish line.

Checklist

• I have opened this pull request against develop
• I have read the contribution guidelines and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog

[DmytroLitvinov]

Should we add it with ^ sign to allow upgrade for minor version in future in package-lock.json file?

[fsbraun]

@vinitkumar Do you have an idea why the javascript tests fail?

[petrklus]

@fsbraun @vinitkumar have you been able to get the bottom of the tests failing?

[fsbraun]

So far, I have not succeeded. @FinalAngel Do you think you can take a look?

[fsbraun]

@petrklus It seems I have closed this PR. I am not certain why and how. Also, I cannot reopen. Can you reopen this PR?

[petrklus]

@fsbraun I think it was closed because the branch django-cms:release/3.11.x was deleted - is there any reason why that happened? Could it please be restored so that I can re-create the PR?

[fsbraun]

OMG, I did not do this on purpose! It's restored now. Is there a particular reason you opened the PR against release/3.11.x? The better way would be to open it against develop.

[vinitkumar]

We will close this PR once #7600 is merged as it does the same thing, but also got the build running.

Also, @petrklus, I added you as a co-author of the commit to properly attribute you for the fix and the initiative. Thanks for helping us figure this one out and of-course of reporting this bug.

[fsbraun]

Fixed by #7600. Thank you, @petrklus, for providing this solution!