* Fix page object

  * Fix page test

  * Provide new translations for getting better information from the
    name strategy
  * Improve a bit the template for displaying errors

The goal here is to immediately display a feedback in the create page
dialog telling the user that the reference is wrong before they click on
create.

I performed following changes here:
  * Refactor CreateActionRequestHandler to have a clean separation
    between retrieving the reference and performing checks over
templates
  * Refactor a bit CreateAction to perform immediate checks over the
    rights and the name strategy before even checking if the template is
chosen: the goal being here to immediately provide exception if there's
a problem
  * Refactor createinline.vm to inject bootstrap modal html elements
    when used with an ajax request: the idea here is to display an ajax
modal instead of the old deprecated xwiki dialog
  * Refactor xwiki.js to use a jquery ajax call to request and display
    createinline
  * Add listener on xwiki:dom:updated events in both create.js and
    select.js to properly load them in case of dom updates

Some work is still needed to display a better information message to the
user, in particular about the strategy that should be used.

* Verify also the given element, not just its ancestors.
* Bulletproofing

[misc] Fix the realtime tests when running on CI (inside the xwiki/build Docker container with Jetty Standalone as servlet engine). In this case we shouldn't map the XWiki aliases to the Docker host but rather to the IP of the xwiki/build Docker container, but we need to determine it.

* Add a UI test to test that reporting works as expected.

This should avoid flickering due to Live Data not refreshing as
expected.

* Don't create a MultiUserTestUtils instance each time it is injected
* Bulletproof test

This is an attempt to reduce flickering in tests that might be caused by
proceeding too quickly with loading other tree nodes while the initial
tree nodes are still loading. Then possibly the selection of the root
node might not be cleared correctly before selecting the desired node as
the root node is automatically selected during the initial load.

* Fix tests.

* Note: it also makes it work with Mysql 9.0

* remove unused import

* Updated the icons on the object and class editors to use current icontheme
* Added a translation for the property move handle
* Removed the alt text for the icon itself and moved the translation to the containing button instead
* Added an icon to the iconTheme, and used it in instead of a hard coded icon from datamodel.
* Fixed format on dataeditors.css
* Set the color of the delete icons to RED
* Removed extra padding from the object title.

* Fix the listener component hint to match the package (thanks @surli )

* Add functional tests for limiting script right and for editing translations
* Move "multi users" tests to RealtimeWYSIWYGEditorIT and use the new multi user test "framework"
* Add page objects to interact with the macro content field on the Macro Edit modal

XWIKI-22309: When creating a new document translation from realtime inplace editor, the content is synchronized with the original translation
* Detect when the current document locale changes without a page reload and update the realtime document locale (that is going to be used to fetch the Netflux channels).
* When creating a new realtime editor, check if the "all users" channel (that is shared) matches the current realtime document locale, and if it does not then disconnect and connect to the new channel.

* Stop submitting the Netflux channel after we disconnect from the realtime session (do proper cleanup).

* Fix a bug in EntityChannelScriptAuthorTracker which didn't lower / update the script level when the target entity reference had initially a low script level (e.g. when two users edit a page whose last author didn't have script right, one of them could use the rights of the other to execute scripts)
* Assume that a request can submit data associated with multiple documents (or document translations) so don't try to determine the entity that is targeted by the request; simply compute the effective author by taking the most recent author with the least script rights
* Update since versions

* Update since version

* Also make sure the CKEditor requests that affect the edited content use the content locale and not the current UI locale because they can differ (e.g. when there's no document translation matching the current UI locale).

* reload the edit mode when switching the edited translation
* change the document locale before locking it (taking care to restore the original translation if the edit fails for the new translation)
* when reloading the document JSON, fallback on the orignal translation if the requested translation doesn't exist
* when rendering the document, fallback on the original translation if the edited translation is new (so that we initialize the content of the new translation with the values from the original translation)

* Add new UITest configuration, named 'servletEngineNetworkAliases', to specify additional aliases that can be used to access the servlet engine running XWiki
* Add a helper MultiUserTestUtils that can be injected in test methods allowing to:
** create new browser tabs and associate them with a given XWiki alias (you can log in different users in each of these tabs)
** switch between the created tabs, taking care of restoring the proper form token and base URL
** close the created tabs (except the first one)
** access the handle of the first (main) tab

* forgot to commut a change