XWIKI-11009: Improve argument passing in Jetty start/stop scripts
+ update XWikiExecutor to stop trying to create a Socket to check if XWiki is running since that could potentially cause some issues (locking the ports temporarily).
* Forgot to close the file... + improve the test

XWIKI-11009: Improve argument passing in Jetty start/stop scripts
+ update XWikiExecutor to stop trying to create a Socket to check if XWiki is running since that could potentially cause some issues (locking the ports temporarily).
* Change the way variables are replaced in jetty start scripts to match what's done by the Maven Assembly plugin. This also avoids an issue with "$!" which was getting replaced by Velocity...

XWIKI-11009: Improve argument passing in Jetty start/stop scripts
+ update XWikiExecutor to stop trying to create a Socket to check if XWiki is running since that could potentially cause some issues (locking the ports temporarily).

This reverts commit c3134ed5.

This reverts commit 333e6ea1.

Reason: The release failed to build due to some dependency problems, so I`m restarting the release.

XWIKI-10829: Executing the import mojo after the package mojo in the same reactor causes the build to fail

Fixed.

* Switch to flamingo in the packager plugin
* Fix some integration tests.

Fixed.

Also fixed the import mojo

Fixed.

Removed non-standard shopt call, since it is not needed and isn't guaranteed to be present in all shell environments

- Removed the previous implementation, since it was causing problems for tests that must run fully offline

Done

XWIKI-10643: Allow the start and stop ports, and additional Java options for the standalone Jetty package to be specified using environment variables
- Using an explicit setting of default value for JETTY_STOP_PORT in BASH, since the standard short-hand way makes the Velocity parser (performed by the xwiki packager plugin) crash.

XWIKI-10650: Having a XWIKI_OPTS environment variable defined breaks the start_xwiki_debug.sh script
Fixed.

[misc] Windows scripts shouldn't be marked executable, because they can't be run on systems that respect the execute flag, and Windows doesn't care about the executable flag

Done.

XWIKI-10648: Remove the log warning about JSP support not being available when starting the standalone Jetty server
Done.

Done.

XWIKI-10646: Make the standalone debug script start in Windows even if JAVA_HOME is not defined and Java is not on the PATH
Done.

Done.

XWIKI-10644: Configure the standalone package not to send the Jetty version in the HTTP response headers
Done.

XWIKI-10643: Allow the start and stop ports, and additional Java options for the standalone Jetty package to be specified using environment variables
Done.

Done.