* Make sure that the 2 builds are executed on the same node, one after another (since the 2nd one depends on the 1st one)

* remove now useless configuration (all builds use Java 17)

[Misc] Build the quality profile with Java 17 since this is needed for SonarCloud ("Starting from the 15th of November 2023, SonarCloud will no longer accept scans executed using Java 11")

Fix Jenkinsfile.

* Simplify code

[Misc] The pipeline logic was changed to keep the last 20 builds for contrib projects. We need to override the config to make it as it was before that change
* "env.BRANCH_NAME" is not available since we're inside a closure called inside xwikiBuild, before any git checkout is done

[Misc] The pipeline logic was changed to keep the last 20 builds for contrib projects. We need to override the config to make it as it was before that change

+ drop the OOB support for Jetty 9.4.x
+ simplify Jenkinsfile since master now builds with Java 11

* Revert to Java 14 since Spoon doesn't work with Java 16....

[Misc] Try to work around the "Java heap space" issue when using the maven assembly plugin for building the hsqldb/jetty flavor. See https://tinyurl.com/45dzmyek
* Roll back the change to see if it helps with the "Killed" job issue

[Misc] Try to work around the "Java heap space" issue when using the maven assembly plugin for building the hsqldb/jetty flavor. See https://tinyurl.com/45dzmyek
* Reduce a bit the memory added since it seems this could be why we now have "Killed" builds in the CI...

[Misc] Try to work around the "Java heap space" issue when using the maven assembly plugin for building the hsqldb/jetty flavor. See https://tinyurl.com/45dzmyek

[Misc] Remove wrong removal of the "repository-all" profile since we need nexus.xwiki.org for the xwiki deps

* Fix bad syntax (again)

* Fix bad syntax

* Add missing commas

[Misc] Make the IT test a real IT test (using the failsafe maven plugin), so that it's executed only once on the CI (for example)
* Differentiate the build name too.

Revert "[misc] We still need to force a recent version of Java in order to be able to run the functional tests using a recent version of XWiki."
Actually it was a bug in the code that processes the Jenkins file that got fixed in the mean time.

This reverts commit ab00f88f.

[misc] We still need to force a recent version of Java in order to be able to run the functional tests using a recent version of XWiki.

[misc] Build the PO before executing the functional (docker) tests (they are not build by the first xwikiBuild because the integration-tests profile is not activated). Also, run the docker tests before the Jasmine integration tests because the later are failing for now.

[misc] It seems the empty profiles value is ignored so let's try with some value that doesn't include the integration-tests and docker. We also need a recent version of Java to run the Jasmine Maven plugin.