* Add unit tests for the page history resources.

Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 5.3.3 to 5.3.4.
- [Release notes](https://github.com/webpack/webpack-dev-middleware/releases)
- [Changelog](https://github.com/webpack/webpack-dev-middleware/blob/v5.3.4/CHANGELOG.md)
- [Commits](https://github.com/webpack/webpack-dev-middleware/compare/v5.3.3...v5.3.4

)

---
updated-dependencies:
- dependency-name: webpack-dev-middleware
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [express](https://github.com/expressjs/express) from 4.18.2 to 4.19.2.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](https://github.com/expressjs/express/compare/4.18.2...4.19.2

)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

XWIKI-19965: Enable the images from new Image dialog Gallery to be selected on double click or with Enter key (#2817)

* Added the listeners for double click and enter key pressed down
* Limited the listener for simple click to avoid collision with the behaviour of the double click one.

Note: This implementation also removes behaviours for click chains higher than 2. I think it's okay to do so because it's rarely even a use case, and removing interaction at this point can actually help users.

XWIKI-22008: CKEditor freezes when editing the page in attempt to change list type for item with image

XWIKI-21219: Add a preparation/compilation pass to the document content and title

* Remove all usages of ControlCharacterFilter as it's been removed in
    xwiki-commons-xml as part of the upgrade

XWIKI-22042: Mail Prepare Thread error still occurs in some cases when triggering the mail sending job from Scheduler

  * Bulletproof usage of #createDocumentDiff by ensuring the docs are
    not null before calling it
  * Fix related test

Change the mechanism of the reset password token to not reset it at each
verification code check, but only when the password is actually reset,
and when its lifetime expired.
Also provide a mandatory document initializer for the
ResetPasswordRequest xclass.

Change a bit more the logic: if the token lifetime configuration is set
to 0 (which was the default) then we automatically remove the reset
password request xobject at first wrong attempt (bad verification code):
it will prevent any bruteforce attack. Then if there's a token lifetime
configuration set, we don't remove the xobject when a bad attempt is
performed: user might have used the wrong mail for example. But we do
remove the xobject when it's expired. And if it's expired, or if the
code was wrong, in both cases we immediately return an error.

Move ResetPasswordIT and ForgotUserNameIT from
administration-test-docker to a new module
security-authentication-test-docker since it's related to
security-authentication module now.

---------

Co-authored-by: Manuel Leduc <manuel.leduc@xwiki.com>

  * Fix integration tests