COR-321 : Document the behavior of restoreIdentity param - SetCurrentIdentityFilter
JCR-2307: ConstraintViolationException expected when a mandatory property is missing and a node with the same name exists

Problem analysis
* When the JCR checks if a mandatory property/sub node exists, it doesn't check for a specific item type such that if we have an existing item with expected name but not the expected type, we won't get the ConstraintViolationException as expected

Fix description
* We now check the name but also the type of the item
JCR-2288: [Cluster] Adding nodes to the same parent node causes TimeoutException

Problem analysis
- The goal of this task is to get rid or limit the risk of getting TimeoutException when we concurrently add nodes to the same parent node in a cluster environment.

Fix description
- When we add a new child node, we have to invalidate the list of child nodes of the parent node in the cache which was done by a simple remove of the related cache entry. The problem with this approach is the fact that this remove was done in a global tx so when it is done concurrently we can face deadlock like in this particular use case. The fix simply isolates the invalidation by doing it outside the global tx in order to highly reduce the risk of such deadlocks. The second part of the fix ensures that if we do a local change, the related commands commit/rollback remain local because before the fix they were replicated even for local changes.
JCR-2312 : Cannot start eXo JCR with MySQL in UTF-8

Fix description:
- Relimit character number of a varchar field if dialect is mysql and utf-8
[PLF-5989] Upgrade dependencies to latest releases
[maven-release-plugin] [PLF-5989]prepare release 1.15.10-GA
[maven-release-plugin] [PLF-5989]prepare for next development iteration
[PLF-5989] Upgrade dependencies to next snapshots
JCR-2332: Remove TestDateSearch inside XLS file

Fix description:
* After COR-329, date value in Microsoft Excel's cells is no longer extracted.
  TestDateSearch inside XLS file gives thus no result.
JCR-2323: Wrong Upload size on cluster mode

Problem analysis:
- On clustering mode : for files whose size exceeds the buffer value (by default 200K), the steps are as follows:
	- The property jcr:data is built in the first node having the value of an object (more precisely of StremValuePropertyData type) that has an instance variable with the name "file" containing the file path in the value storage and point on a path in the swap file.
	- When this property is applied to the second node and the object is intercepted, the logic responsible for the serialization of the object simply checks if the file exists in the system or not (which is not the case) and make it "null" if necessary.

Fix description
- When the  path file of StremValuePropertyData is null, do forceLoad the property data from the DB storage.
JCR-2326: jcrvdxxxxxxxxxx.tmp temporary files are not deleted after uploading a file

Fix description:
- Release all pointers targeting to tmp file then Garbage Colllecter clean it.
Merge branch 'stable/1.15.x' of github.com:exoplatform/jcr into S3
Integrarted changes from JCR-2347
Upgraded to AWS 1.9.0, fixed the connection leak issue and added some unit tests
JCR-2347: Fix TestCacheableWorkspaceDataManager.java
Add max-connections to avoid connection reset
Reduce the total amount of queries
JCR-2347: Allow to Spool content if required
Ask to spool content for performances reason
merge with exodev/S3 02a4d6664b8e9db9fc03160c48eee8cfd4840211