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

This test is incorrect as the assertion checks equality on the same reference

* feat(deps): update dependencies

Xstream from 1.4.17 to 1.4.18
Postgresql driver 42.2.5 to 42.2.13

* Change tests so that tests ignore whitespaces when comparing xmls

when deleting a tenant, we must empty the tables in the order:
* business_app_menu
* business_app_page
* business_app

otherwise, the foreign keys are violated

To avoid an constraint violation on business_app_menu that references itself (parent/child menu), we tried adding an `ON DELETE CASCADE`.
Because of SQL server, we can't add an `ON DELETE CASCADE` on a table that references itself.
https://stackoverflow.com/questions/38977004/sql-server-table-with-foreign-key-to-itself-with-cascade-delete
As a work around, we deleted first all business_app_menu that have a parent (1 level of menu only) and then all others

for init tenant creation scripts

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

some tests do not uninstall the BDM so we must ensure it's cleaned before
installing it again.

We had a fork on the `JarFileClassLoader` of Xbeans. It looks like it had some issues that were fixed in the JVM's `URLClassLoader`. see https://bugs.openjdk.java.net/browse/JDK-6832540

We do not rely anymore on features provided by the `JarFileClassLoader`.

Replace the parent class of our `BonitaClassLoader` from that classloader to `URLClassLoader`.

We might be able to remove some additional handling of non-jar resources as well.

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

They were used in web project at some point but not anymore.

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

They were used only in tests.

+ remove unused code from ProfileMemberUtils (server side)

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

* Remove unexistings commands
* Remove 'delete session' command only used in tests

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

This dependency is used both by web-extension and distrib, put it here in order to have no duplication on the servlet api version

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

Instead, change the serializer to make it not export profile entries.

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

this object is deleted in 7.13.0

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

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

Due to migration strategy changes, the message will never be printed when
started after a bonita update.

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

* feat(page permissions): Update page permissions

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

remove test module and add yaml module

* completely remove server code (service, database table, ...)
* deprecate client-side code

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

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

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

* remove the possibility to update the page name on updateContent() and updatePage() methods.
* Deprecate field  `PageUpdateField.NAME` 
* refactor code to have less database calls
 
Closes [RUNTIME-385](https://bonitasoft.atlassian.net/browse/RUNTIME-385)

This comimit also refactors calls to page update calls so that we do not retrieve several times
the same object within the same Hibernate session.

There seems to be a problem when trying to update several times the same object
within the same Hibernate session. Maybe because we do it once on the object WITH
content, and then 2 other times on the same object WITHOUT content.

So this commit simplifies that by updating the object only once.

defect(PageImport): Removable and Editable was not updated if page is still provided when content is different (#2050)

* chore(PageImport): develop the mvp for release 7.13
* add new editonly and final page if page is absent
* add removable page only in case of all final page are added meaning that is a first run since a Bonita update, a tenant creation or an installation from scratch
* update of editonly and removable pages only in case of the provided flag is true.

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

for Community subtree

Replace pluginManagement section in first place in settings.gradle

* add a check that verifies if the non-removable pages are already present, if not that means that it is the first start and the removable page must be re-imported.

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

* allow the system only to update a non-editable page
* test code cleanup: some tests passed for a bad reason due to expected exception handling
* slightly modified message when page cannot be updated / removed

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

Add a check that verifies if the final apps are already present, if not that means that it is the first start and the removable page must be imported.
This will also import the default apps at the first start after migration.

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

* theme
* layout
* icon

should be updatable anyways, even for non-editable apps

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

It is used in the distrib by a module

The import of the application was setting the mime-type to `empty` instead of null. Because of that, the front-end was believing that an icon was present.

Add more input validation when creating/updating the application.

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

the `ApplicationImportStrategy` returns now an enum `ImportStrategy` that gives the action that must be done with the application in case it already exists.
There are 3 possible actions:  
* `FAIL`: it stops the import and throws an exception
* `SKIP`: the application is not imported without errors
* `REPLACE`: the application is deleted then imported


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

In addition, use an MD5 sum instead of a java `Arrays.hashCode`

This is more portable to use an algorithm that is well known instead of relying on a JVM method.

having the has as String will having a failure when the content of the field is null during the migration.

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

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