* forbid XAR dependencies in JAR and WEBJAR extensions by default

(cherry picked from commit 62db0e64)

Use a generic method to detect if the edit form field is visible to the user, the previous way was creating flickers.

(cherry picked from commit b389120d)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Cherry-pick test framework changes from platform in order to be able to run the PDF export functional test.

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Add support for the case when XWiki itself also runs inside a Docker container (DOOD). Fix failing functional test on CI
XWIKI-19873: Add support for using a remote Chrome instance for PDF export

(cherry picked from commit 0c299363)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Add configuration to control whether the Chrome Docker container is reused (managed) or not. Default to false (i.e. drop the container when XWiki stops)
* Rename getChromeDockerHostName to getXWikiHost, because XWiki may not run on the same machine as where the Chrome container runs (XWiki may be itself in a Docker container)

(cherry picked from commit b3641b3e)

  * Move the CSS property in xwiki.selectize.css so that it's available
    in every picker

(cherry picked from commit 0c1e64f3)

XWIKI-19451: Edit control cannot be reached for livedata for columns which are much larger than their content

Make the tooltip follow the cursor horizontally to minimize the distant to access the actions.

(cherry picked from commit 4fe44d29)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix issue reported by sonarcloud (use try-with-resource for CreateContainerCmd)
* Connect to the headless Chrome using the IP of the Docker container instead of localhost (required when the XWiki instance is also inside a Docker container)

(cherry picked from commit 71a803c2)

Use waitUntilElementIsVisible instead calling find to assert if the no result warning message is displayed to allow for retry in case the message takes time to become visible.

* We need to add localization-webjar and localization-rest-default to the minimal WAR because job.js from platform-web-war was refactored to use the xwiki-l10n JavaScript module. Moving job.js outside platform-web-war is not easy without a proper skin extension plugin to load files from WebJars.

(cherry picked from commit a8d85593)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Make sure to close resources (reported by sonarcloud)

(cherry picked from commit 866d27cd)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix the quality build by specifying the test coverage ratio (it's 0 because this module is almost empty).

(cherry picked from commit 7cf70caa)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix pom version after cherry-pick

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix the order of the printed documents

(cherry picked from commit 8fe51ff1)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Make the test content pages non-hidden (for now we print to PDF all child pages but in the future we may want to filter out hidden pages).

(cherry picked from commit 68459a13)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Remove duplicate dependency.

(cherry picked from commit 8403ee0e)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Extend the page objects and the tests
* Modify flavor-test-misc to use the PDFDocument class in order to avoid code duplication.

(cherry picked from commit 82df10e0)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix the way the cookies are saved and restored on on the PDF job context
* Extend the page objects
* Add more functional tests

(cherry picked from commit 09f7eec7)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Add test page objects and Docker-based functional tests
* Fix some issues raised by the functional tests

(cherry picked from commit a11b72bc)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* More tests

(cherry picked from commit f9eb495e)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* More tests

(cherry picked from commit 9d3ff13e)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Add unit tests

(cherry picked from commit 0a0087ef)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Improved logging

(cherry picked from commit a0732471)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Force the 1.0 version of the WebSocket API because we're still supporting Jetty 9.4.x and cdt-java-client seems to be compatible with 1.0 version even if it depends on 1.1

(cherry picked from commit 19367770)

(cherry picked from commit 3f350a95)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Read smaller chunks from the PDF "stream" in order to avoid a BufferOverflow exception raised by the Tyrus (WebSocket) client used to communicate with the headless Chrome browser.

(cherry picked from commit 85ff7df0)

(cherry picked from commit c9447d81)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Notify the user that the PDF export failed rather than redirecting to a missing file.

(cherry picked from commit 8123ddcf)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix the empty PDF ToC (look for the job status also on the jobs that are currently in execution)
* Allow only HTTP URLs for printing
* Set the base URL before printing to PDF to make sure the relative URLs in the generated PDF are resolved based on the original URL.

(cherry picked from commit dc737df3)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Set cookies in order to authenticate the user and isolate the Chrome tabs using separate browser contexts.

(cherry picked from commit 52183cbc)

XWIKI-19270: Add support for performing the PDF export using a browser running in a Docker container
* Fix the way we serve the generated PDF as an input stream (we need to convert the bytes to unsigned int in order to not conflict with the end of stream)

(cherry picked from commit 4cfaac27)