XWIKI-11507 : Integrate the ratings system from xwiki-contrib
- created new xwiki-platform-ratings module
- prefixed the modules from xwiki-contrib with 'xwiki-platform-ratings-'
- changed main pom parent from 'xwiki-commons-pom' to 'xwiki-platform-core'
- changed the artifact id from 'application-ratings' to 'xwiki-platform-ratings'
- changed package name from 'org.xwiki.contrib.ratings' to 'org.xwiki.ratings'
[misc] xar:format xwiki-platform-ratings-ui
- add missing licenses
XARATINGS-10 : Storing ratings in separate spaces is failing
XARATINGS-4 : Allow admins to choose in which space the app will be active
- drop the JS injection and move the code which handles the rating display into a UI Extension
- this would make the code cleaner and easier to read properties from a configuration object due to not having to make a request to get those parameters
XWIKI-11507 : Integrate the ratings system from xwiki-contrib
- ensure retro compatibility with the version of this module from xwiki-contrib
XARATINGS-4 : Allow admins to choose in which space the app will be active
- added a configuration class
- added XWiki.RatingsConfig as the global configuration file
- to configure the ratings on a specific space there has to be a XWiki.RatingsConfigClass object on the WebPreferences doc of that space
- the settings defined on a space have precedence over the ones from XWiki.RatingsConfig
- fallback to xwiki.cfg and xwiki.properties properties has been maintained (priority: space -> wiki -> xwiki.preferences -> xwiki.cfg)
- updated the UI Extension to be aware of the configuration objects
XARATINGS-4 : Allow admins to choose in which space the app will be active
- by default, ratings should be deactivated in the global config
[build] Fixed parent version.
XWIKI-11552: Suggestion lists of 'suggestDocuments' and 'suggestSpaces' inputs get hidden when overflowing the 'xwikicontent' parent's height
- Using the default parentContainer.
[misc] Make sure the copy-webjar-resources and minify-webjar-resources executions are not run by default. Unfortunately there's no other way to reuse executions: we need to specify the phase everywhere.
[misc] Fix yuicompressor default config and run JSHint on the tree webjar.
* Use the .min suffix in the default yuicompressor configuration because it's a best practice.
* Add support for running JSHint on JavaScript code at build time.
* Fix JSHint errors in the job and tree webjars
* Use strict JavaScript in the job and tree webjars
XWIKI-11517: Enable default actions for the Flamingo top menu entries
XWIKI-10708: Allow LESS syntax in SSX.

* Big refactor
XWIKI-11518: Infinite recursion displaying the title of the hourly watchlist job
* Apply new XAR format.
XARATINGS-4 : Allow admins to choose in which space the app will be active
- due to the fact that now the topmost configuration source is dynamic (Space.WebPreferences) we have to update the methods that retrieve configuration parameters to not depend on the context for retrieving the document for which the ratings are set/get but on the passed document name
- using the context to determine the document on which the ratings are set/get would not work when the context is anything other than the document that has the ratings associated to it
-- for example when calling from REST
XWIKI-11518: Infinite recursion displaying the title of the hourly watchlist job
* Improve the #sheetTitle macro to support a common use case: displaying the sheet title only when the current document has an object of some type
* Improve the title of the SchedulerJobSheet
* Remove the usage of the deprecated EditModeClass on the SchedulerJobSheet
* No need to include the sheet in the content of the SchedulerJobTemplate and the default WatchList jobs
XWIKI-10708: Allow LESS syntax in SSX.

* First implementation of SSX using LESS.
* Todo: a cache cleaner when a SSX is saved.
XWIKI-11517: Enable default actions for the Flamingo top menu entries
* Update test page objects.
[misc] Use the improved webjars API (that removes the need to specify/hardcode the version).
XWIKI-11543: Integration of requirejs should be provided through a dependency on its WebJar
* Remove the require.js file bundled with xwiki-platform-web
* Modify javascript.vm (both in platform-web and flamingo-skin) to load RequireJS as webjar
* Declare dependencies to RequireJS and JQuery webjars.