Currently translated at 100.0% (4 of 4 strings)

Translation: XWiki Platform/Jetty listener
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/jetty-listener/fr/



Co-authored-by: Simon Urli <simon.urli@xwiki.com>
Co-authored-by: raphj <raphael.jakse@xwiki.com>

* Add a new method `getRequiredRight` to `MacroPermissionPolicy` and implement it for the different script macros
* Introduce a RequiredRightAnalyzer role to analyze the rights that are required by a document, macro or XObject
* Add generic analyzers for macros and objects
* Add generic script macro support
* Add an analyzer for XWiki.RequiredRightClass
* Add an analyzer for skin extensions
* Add a component for printing the content of an XObject
* Add a component for printing macro parameters and content.
* Introduce RequiredRightsEditConfirmationChecker
* Introduce RequiredRightsAddedFilter to filter results according to the document author
* package the UI by default in xwiki-platform-distribution-flavor-common
* Minimal docker test + Page objects
* Introduce a configuration to enable the required right analysis, disabled by default as long as it is incomplete and not polished
---------

Co-authored-by: Manuel Leduc <manuel.leduc@xwiki.com>

* Replaced all div with id mainContentArea by main elements
* Changed the position of the main content on pages where it needs to be more specific (e.g. view, now main only has the text, and ToS users don't need to go through the breadcrumb on every use)
* Removed the hierarchy from main on multiple pages.
* Fixed the main size on pdfoptions.vm
* Updated the test resources
* Set the #mainContentArea on all the previously defined `main` nodes.
* Tried to fix some display issues

* Replace the xwikiHost configuration with xwikiURI in order to allow specifying the scheme/protocol and port number besides the domain name or IP address.

XWIKI-21170: Improve the error message shown when the PDF export size limit is exceeded
XWIKI-20881: Don't enforce the size limit on single page PDF exports

* Cache failures
* Properly dispose the caches
* Only send requests to trusted domains
* Only embed actual images
* Limit responses to 1MB
* Introduce configuration options for timeout, maximum size and if the
  feature is enabled at all
* Add a UI test that checks that attachment embedding is working in
  general
* Move to httpclient5
* Expose the cookie domains configuration in AuthenticationConfiguration

* Finish removing things I had missed + add missing revapi violations (thanks Simon)

  * Remove the property from xwiki.properties.vm and the only usage of
    it in XWiki.java
  * Move all deprecated APIs that are no longer used to legacy
  * Add revapi ignores related to aspectj bug (see:
    https://github.com/eclipse-aspectj/aspectj/issues/246)

* Moved to https://github.com/xwiki-attic/xwiki-platform-chart-plugin

  * Move code and components for live email notifications with
    post-filtering to legacy modules
  * Deprecate configuration method related that check if prefiltering is
    enabled as it's now the standard
  * Remove the configuration from xwiki.properties to turn off
    prefiltering
  * Move deprecated NotificationManager to legacy
  * Move the API NotificationConfiguration#isEventPrefilteringEnabled to legacy and every implementations relying on it too

Co-authored-by: Thomas Mortagne <thomas.mortagne@xwiki.com>

XWIKI-21011: Mail resender script service API resends all mails when called from a subwiki
XWIKI-21015: Missing legacy instance APIs in distribution
* Also add missing EM categories
* Fix typo in MailResender.xml (in the "from" test)
* Make the resender scheduer job execute as XWiki.superadmin
* Male the MailResender.xml document customizable instead of demo to avoid deleting it (it's now an official feature)
* Add debug logs when resending mail
* Fix mail resender scheduler typo in description

Previous work was about introducing strategies to group events for creating
composite events. This work is about strategies for chosing how many
mails should be sent for each composite event to notify by email.
Historically the strategy was hardcoded and consisted in putting all
composite events in the same email. Here we provide different
strategies: the previous one, but also a strategy allowing to send one
email per composite event, and another one allowing to send a separate
email specifically for mentions.

That work also improves previous API to use a clear UserReference
instead of a String which is vague.

Co-authored-by: Manuel Leduc <manuel.leduc@xwiki.com>
Co-authored-by: Thomas Mortagne <thomas.mortagne@xwiki.com>

XWIKI-20937: Add support for configuring an user property to be displayed as hint by the user picker

Currently translated at 100.0% (4 of 4 strings)

Translation: XWiki Platform/Jetty listener
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/jetty-listener/uk/

* update documentation