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

* put applications zip in classpath
* put application pages in classpath
* remove unneeded resources
* add final directory for non-nodifiable / non-deletable atrifacts
* add editonly directory for modifiable / non-deletable artifacts

covers [RUNTIME-248](https://bonitasoft.atlassian.net/browse/RUNTIME-248)
covers [RUNTIME-263](https://bonitasoft.atlassian.net/browse/RUNTIME-263)
covers [RUNTIME-183](https://bonitasoft.atlassian.net/browse/RUNTIME-183)

in order for Studio to freeze all runtime dependencies to
the versions the runtime pull (directly or transitively)

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

* remove the token placeholders that were used by IT tests in bonita-web-sp module
* remote portal is not allowed anymore so bonita.war(-sp) already contains bonita-engine(-sp)
* fix up some transitive dependency version

* comment AJP connector by default (follow tomcat changes)

this fixes CVEs, see
https://tomcat.apache.org/security-8.html

Closes [BR-408](https://bonitasoft.atlassian.net/browse/BR-408)

Thomas Bouffard authored Jan 15, 2020 and Baptiste Mesta committed Jan 15, 2020

Stop having bonita-web as parent
  - this added gwt dependencies to all modules
  - use bom for dependencies management instead

remove declaration of uid version as it is not used (confirmed by the version
which relates to bonita 7.6)

upgrade plugins versions to latest available
remove unused plugins
  - checksum-maven-plugin
  - jacoco-maven-plugin

update maven-compiler plugin configuration

Introduce bonita-war to replace all-in-one and war-server
  - the main change is to declare all dependencies in war-server to let maven
  resolve dependencies
  - only on community for now
  - previously, as we copied the lib from the web war and add the one for
  bonita-server, the dependencies resolution could not be properly done by maven
  So, now, just copy web resources first to create the initial war, then add all
  the lib to the war via full maven resolution

Simplify the bundle preparation
  - previously, it was done in several steps because we had the deploy and the
  wildfly bundles.
  - now, we create a 'tomcat distribution for bonita', used for both Community
  and Enterprise to remove duplication

Other changes
  - remove license files
  They are only packaged in the deploy bundle but not in the final tomcat one,
  so remove them
  - remove spnego jar from repository and get it as maven dependency
  - package: avoid warning on windows (outputDirectory)

It was not packaged in the bundle nor made available outside of this repository.
As of Bonita 7.10.0, it is now hosted in its own repository:
https://github.com/bonitasoft/bonita-user-application