Changes

Bug #15018 Fix vulnerability by using a volatile per-page token and by removing useless request parameters and web controller attributes

In order to enforce the security while managing user domains in
Silverpeas, a specific volatile synchronization token mechanism is used.
Each time a change (id est a side-effect action) is requested, the
client must pass a token that has been specifically generated for it
before; only expected clients (web pages in the Silverpeas  backoffice)
are mandated to receive this token and the token is renew each time.

Refactor the sort order attribute as an enum in order to avoid invalid
values. Remove useless parameters and attributes in the search.

Bug #15110

When qualifying the reported issue, I found the status of a user (in his
profile) wasn't correctly escaped when rendering by one of his contacts.
I fixed then this.

Fix support #15091

Buttons displayed was not screened good

For Quality Gate

Unexpected shorthand "background" after "background-color"

Bug #15125

The publications weren't really sorted. This is now fixed. Keep track
also of the sorting rule chosen by the user.

Bug #15153
Bug #15146

When notifying subscribers about the creation of a new classified, the
concerned subscribers are fetched according to the component instance
for which the subscription has been done.

Sort the list of values for each fields targeted by a subscription
before rendering them.

Bug #15115

The ui-resizable-handle needs an Id contained kmelia  to appear

bug #15156 : Updating end date of the project can provoke a without-end loop.

bug #15063 : The images inside of a wysiwyg field content is now well managed (URL changed with the new attachmentId and new app Id)

Bug #15118 Fix bug by redefining with var the scope of the
searchEngineScope, directoryScope and searchScope variables.

feature #15131 : activation of a planned compacting task during execution