* Fix the typo

XWIKI-18600: Refactor the security modules organization, add a Security Config component and improve some templates
* Make it work better...

- follow best practices when logging the exception as warning

- forgot to add test in last commit

- avoid the error for adding an empty page name
- also raise log level for failures to get the
  events from the EventStore to make them more visible,
  as querying the database can come with a notable
  performance penalty

  * Ensure to rely on the textarea content type for setting the syntax
    in TExtAreaClass#displayEdit
  * Refactor a bit simpleedittoolbar.vm to rely on $edit.data.syntax if
    it's defined, instead of relying on $doc.syntax.

  * Check for both /view/ and /get/ action to serve the
    documentdoesnotexist template which handles settings the 404 error
status in XWikiAction

* require API part to be installed on root name space

XWIKI-19276: Cannot update to XWiki 13.10.2: "Index column size too large. The maximum column size is 767 bytes"
* add missing since annotations

XWIKI-19276: Cannot update to XWiki 13.10.2: "Index column size too large. The maximum column size is 767 bytes"
* moved DYNAMIC raw type migration first
* also removed R130200001 migration which does the exact same thing

XWIKI-17793: Users cannot continue typing seamlessly after inserting a mention with the '@' shortcut
XWIKI-19236: Mentions are not inline where inserted in an empty line
* Enforce the inline mode when inserting the mention macro using the @ shortcut. This also moves the caret after the macro.

XWIKI-18717: NPE in 'xpart.vm' when adding comments with CAPTCHA as guest user which causes errors in browser and prevents adding further comments

  * Bulletproof commentfield.vm to ensure to not perform API call with
    null parameter value
  * Bulletproof BaseClass#addField to ensure to not obtain a NPE in case
    it's called with a null value, and to log a warning in such case

Ecaterina Moraru (Valica) authored 4 years ago and Vincent Massol committed 3 years ago

* Displaying a sponsor button in your repository, read documentation at https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
* Using the OpenCollective service, see https://opencollective.com/xwiki