* either support old mode with separator or contentName attribute for
json file upload response

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

* avoid stacktrace in the logs incase the page

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

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

covers [RUNTIME-371](https://bonitasoft.atlassian.net/browse/RUNTIME-371)

* display a 404 when targeting /bonita/apps and /bonita/apps/ instead of a 500 currently
(when getPathInfo  is null)

* when the 404 in on a resource (css, js...) and not a page the
redirection to the 404 page should not be attempted. As a result, the
method sendError should only be used for pages. Otherwise we should use
setStatus(404)

* remove duplicate 404 handling

* avoid issue when calling sendError and the response has already been
committed

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

* feat(APIID): Use and catch new APIItemIdMalformedException instead of APIException

covers [RUNTIME-344](https://bonitasoft.atlassian.net/browse/RUNTIME-344)

* fix(APIID): Don't throw error in logs and only return an API response

covers [RUNTIME-344](https://bonitasoft.atlassian.net/browse/RUNTIME-344)

* Add test

* Check id in specific places (Human task id and Actor member)

* redirect old homepage servlet URL to app drectory URL for backward URL
compatibility

relates to
[RUNTIME-112](https://bonitasoft.atlassian.net/browse/RUNTIME-112)

* chore(deps): upgrade jackson to 2.12.3

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

* remove jackson version: we use the bom instead

"deployAtEnd does not work with unrelated projects"
cf. https://www.robinhowlett.com/blog/2019/05/15/solved-when-the-maven-deploy-plugin-silently-fails-to-deploy/

newly introduced bom module broke the deploy, because it has no common parent pom.
The workaround is to explicitely declare in it the Maven deploy plugin.

* grant access to super admin and app directory applications

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

* attempt to replace homepage servlet with app directory
* fix oidc test

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

* handle update and delete page api exception
* remove test on page provided field
* update the code to avoid update of permission and ressource in case of exception happened on call of pageApi.update or pageApi.delete
* add junit test that check no interaction happen before an api exception
* CustomPageService.ensurePageFolderIsPresent was not done now in   `removeRestApiExtensionPermissions` method. It should be done before the `removeRestApiExtensionPermissions` called

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

* remove GWT mockito global dep
* remove xerces dependency in 6.x forms
* restore gwtmockito in projects which needs it
* restore javassist version 3.22 just for GWT tests (GWT mokito is not compliant with 3.27)
* fix server tests that were using gwt transitive deps

* adapt MultiReadHttpServletRequest to servlet spec changes

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

Add new fields on the application:
* editable field
* visibility field

covers [RUNTIME-286](https://bonitasoft.atlassian.net/browse/RUNTIME-286)

So that there is no need to redefine the version when declaring the dependency.

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

so that there is not private BOM (that would be harder to pull in Maven)

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

with weird / unused artifacts

BOM = Bill of Materials

* org.bonitasoft.console:bonita-web-bom
* org.bonitasoft.console:bonita-web-sp-bom

these boms contains all runtime dependencies used by the web modules

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

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

* avoid creating the HTTP session in case of a SAML authentication as informations stored in it by keycloak are lost
This is not a big issue for most use cases as, once you get a bonita session, we don't go through keycloak filter code. However for some features like global logout, this may be an issue if you use POST response binding.
Also, it appears that Keycloak already provide a mechanism to recreate the session when logging in with the option turnOffChangeSessionIdOnLogin="false"
* update keycloak conf example

Cover [RUNTIME-293](https://bonitasoft.atlassian.net/browse/RUNTIME-293)

* Return the bdm information instead of the filePath when uploading a new bdm

covers [RUNTIME-70](https://bonitasoft.atlassian.net/browse/RUNTIME-70

)

Co-authored-by: Emmanuel Duchastenier <emmanuel.duchastenier@bonitasoft.com>