* Replaced inline styling with regular style for the panel wizard tooltip
* Removed the comment from the test for the panel wizard

* Added a missing space between attributes in the pdf generator select
* Replaced the comment with an actual test for the export PDF section

* Fixed a `label` copy pasted too fast: the for attribute did not get updated.
* Removed the comment from the test for WYSIWYG

* Update webstandard test pages
* Updated the .pom with references to jira tickets for each page

* Added back the removed tests.

Currently translated at 100.0% (23 of 23 strings)

Translation: XWiki Platform/Tour.HomepageTour.Translations
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/tour-homepagetour-translations/ko/

Currently translated at 100.0% (23 of 23 strings)

Translation: XWiki Platform/Tour.HomepageTour.Translations
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/tour-homepagetour-translations/ko/

Currently translated at 69.5% (16 of 23 strings)

Translation: XWiki Platform/Tour.HomepageTour.Translations
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/tour-homepagetour-translations/ko/

Currently translated at 100.0% (2 of 2 strings)

Translation: XWiki Platform/Main.WebHome
Translate-URL: https://l10n.xwiki.org/projects/xwiki-platform/main-webhome/ko/

  * Add a new migration to properly save the old WatchListClass objects
    as filter preferences using the NotificationFilterPreferenceStore
  * Reuse the logic provided in the old bridge for performing the
    migration
  * Get rid of the the watchlistbridge module as it was only containing
    the component for performing the bridge
  * Fix error in the migration
  * Use a TaskConsumer for performing final clean up of the objects
  * Migrate autowatch property to a new Autowatch xobject whenever
    that one doesn't exist and there's a WatchListClass xobject before
removing it, as we use to fallback on those xobject properties in
DefaultWatchEntitiesConfiguration
  * Fix test DefaultWatchEntitiesConfiguration and refactor it

* Added a sr-only title for wiki and wysiwyg pages
* Removed two empty pages from the distribution flavor tests...

Note: Looking at the failure reports on CI https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/stable-15.10.x/34/testReport/junit/org.xwiki.test.webstandards/CustomDutchWebGuidelinesValidationTest/Platform_Builds___main___distribution___flavor_test_webstandards___Build_for_Flavor_Test___Webstandards_______22/ and https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/stable-15.10.x/34/testReport/junit/org.xwiki.test.webstandards/CustomDutchWebGuidelinesValidationTest/Platform_Builds___main___distribution___flavor_test_webstandards___Build_for_Flavor_Test___Webstandards_______53/ ), it seems like there is no content on those pages (search for `mainContentArea`). Therefore I don't see a problem in removing them from those tests.

* Removed H1 from the Dashboard sections
* Removed H1 from the Panels
* Fixed the home page header level
* Removed multiple h1s from the user profile sections
* Updated the content of the sandbox page
* Removed a style rule that is just extra as of now
* Updated translations to follow the changes applied in the English files
* Updated the administration section title to a H2 (see Editing -> Wysiwyg editor )
* Updated CSS to avoid backward incompatibility

[misc] Exclude optional jdbc connectors dependencies (they are not supposed to be needed in XWiki context and they can cause conflicts)

If the service is running, we need to restart it in any case, no matter if
it's enabled or not.
However is-active does not always seem to work if the package just gets
installed (see XWIKI-18624), so also check if it's only enabled and try to
restart it then.

* fix bad virtual package names

* the xwiki webapp was not properly registered in jetty
* the xwiki service was not enabled at install
* store the log in /var/log/xwiki
* various minor improvements

* add a working directory to the unit file
* the start and stop script are using bash

* missing search and replace

* 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>

* Fixed outdated functional tests