Set the system property `bonita.runtime.logger.sysout` to `Console` or `Console-JSON`

By default the bundle does not log to the system out.

Closes [RUNTIME-795](https://bonitasoft.atlassian.net/browse/RUNTIME-795)

We were using other dependencies.

The dependency is directly in /lib/bonita folder, that's why we exclude it from the war.

* use now  [eclipse-temurin](https://hub.docker.com/_/eclipse-temurin?tab=description) instead of adoptjdk as base docker image that is now the official docker images supported by dockerhub.

If we log both to console and `bonita.log` file, when we start the tomcat
bundle using `startBonita.sh`, it makes logs written both to
`bonita.log` and `catalina.out`. It's better to only log to `bonita.log`
This was the behavior since at least 7.11

That change must be documented because when running the bundle using
`catalina.sh run` it does not log to the console anymore.

bump tomcat version to 9.0.56 to fix cve [CVE-2021-42340](https://security.netapp.com/advisory/ntap-20211104-0001/)

Relates to [RUNTIME-688](https://bonitasoft.atlassian.net/browse/RUNTIME-688)

* bump log4j2 to 2.17.1 to fix cve [cve-2021-44832](https://checkmarx.com/blog/cve-2021-44832-apache-log4j-2-17-0-arbitrary-code-execution-via-jdbcappender-datasource-element/)

* bump log4j2 version to integrate last log4j2 fixe of [CVE-2021-45105](https://logging.apache.org/log4j/2.x/security.html)

* using adoptopenjdk/openjdk11:jdk-11.0.11_9-alpine-slim instead of ubuntu to have an images of a smaller size and more secure
* install jattach directly from  alpine/edge/community/
 repository

For subscription image, chmod/chown are done in the build stage to avoid file duplication afterward

Covers [RUNTIME-497](https://bonitasoft.atlassian.net/browse/RUNTIME-497)
Covers [RUNTIME-548](https://bonitasoft.atlassian.net/browse/RUNTIME-548)

cherry pick commit 872fd7d and 5aeb603 PRs #430 and #431  to enable formatMsgNoLookups to mitigate impact CVE-2021-44228 with custom client's code

* fix(datasource): make proposed changes to datasource
* specify removeAbandoned="false"

Relates to [RUNTIME-495](https://bonitasoft.atlassian.net/browse/RUNTIME-495)

* bump log4j2 version to 2.15.0 to fix [https://github.com/advisories/GHSA-jfh8-c2jp-5v3q](CVE-2021-44228)

* feat(logging): integrate feedback on log4j2 configuration

* Add logging format from 2021.2 and before commented in
  `log4j2-appenders.xml`
* Remove `logging.properties` from tomcat
* In tomcat, by default log also in the console output as before
* Remove the automatic deletion of logging file: we should not delete
  them by default
* Reformat logging files

Relates to [RUNTIME-606](https://bonitasoft.atlassian.net/browse/RUNTIME-606)

* add permission on /opt to be compatible with bonita cloud
* chore(docker) : change permission on /opt to be more compatible with BonitaCloud
* Bonita Cloud use a volume bind on /opt/bonita run. To allow that, the permission on /opt must be change to give write authorization to other.
* remove no more needed volume

# Conflicts:
#	community/tomcat-resources/bonita-tomcat-juli/pom.xml

Covers [Runtime-655](https://bonitasoft.atlassian.net/browse/RUNTIME-656)

Make JMX available in docker image & tomcat bundle, not activated by default, with auth by default.

activate by env variable `JMX_REMOTE_ACCESS=true`

Covers [RUNTIME-550](https://bonitasoft.atlassian.net/browse/RUNTIME-550)

* the config files `log4j2-appenders.xml` and `log4j2-loggers.xml` are no more magically copied and are now located in `/opt/bonita/conf/logs`

* the basedir for logs files is now `/opt/bonita/logs/` in case file appender is activatedd

Covers [RUNTIME-636](https://bonitasoft.atlassian.net/browse/RUNTIME-636)
Covers [RUNTIME-627](https://bonitasoft.atlassian.net/browse/RUNTIME-627)

* refactor(log): restore same log levels as in previous minor version

+ fix bug in org.hibernate.SQL_SLOW logger name
+ add info on static permission log level tracking

Relates to [RUNTIME-606](https://bonitasoft.atlassian.net/browse/RUNTIME-606)

That period was poluting logs in case of a xa resource that is not
recoverable.
This can happen when a arjuna is commiting an XA transaction but the
connection fails at that time. In that case Arjuna does not know what to
do with the XA transaction and tries to recover it each time (it is in
HEURISTIC_HAZARD state). This happens even if there is a single
resource. In that case, it requires an human action to remove the
resource form the transaction log.

Set that period to 2 hours by default to reduce the impact on logs while
keeping the issue visible.

Relates to [RUNTIME-45](https://bonitasoft.atlassian.net/browse/RUNTIME-45)
Relates to [RUNTIME-625](https://bonitasoft.atlassian.net/browse/RUNTIME-625)

default web.xml added with 60min session-timeout.
The change was needed to match with bonita config:
#bonita.tenant.session.duration=3600000

The timeout is set while building the bundle zip

Closes [RUNTIME-117](https://bonitasoft.atlassian.net/browse/RUNTIME-117)

Previously, when attempting to recover a XAConnection, no new connection was initialized. The recovery failed, and was retried indefinitely.

We now check if there is an active connection, attempt to close it properly and then create a new one.

Closes [RUNTIME-45](https://bonitasoft.atlassian.net/browse/RUNTIME-45)

* add log4J2 libraries and logger configuration file to the distrib ( bundle )
* make docker **community** and **subscription** works well with log4j2 and have the possibility to hot change log levels

closes [RUNTIME-523](https://bonitasoft.atlassian.net/browse/RUNTIME-523)

* there is no conflict with commons-collections
* commons-logging and commons-codec seem to be uses in a different version in bundle-test only but bundle-test depends on bonita-client only and those are server dependencies

Allow to specify the user with docker run parameter `--user`.

Doing this will change the user with which the container is run.
If the user given is not root, we do not try to change some of the folders ownership using `chown` or `chmod`.
To allow this behavior, at docker build, we open access rights of few folders to 777 (all users can do anything) and then restrict them if we are root at startup. This is a common strategy to support that. See:
https://github.com/docker-library/postgres/pull/253


This comes with some limitation: mounted folder need to have correct access rights configured when running with this option

Closes [RUNTIME-547](https://bonitasoft.atlassian.net/browse/RUNTIME-547)
Relates to [PF-6998](https://bonitasoft.atlassian.net/browse/PF-6998)

That property was used when the dbtool was here

Relates to [RUNTIME-544](https://bonitasoft.atlassian.net/browse/RUNTIME-544)