Improvement EZP-22191: Change Criterion\LanguageCode to match alwaysAvailable content by default
Improvement EZP-22191: New \$useAlwaysAvailable argument for ContentService methods with language filtering

The bahavour is not enabled by default in this commit as this is meant for backports.
BC break when changing the default is that any code expecting to get exception when
not a specific translation exists will break if content is always avaiable and main
language is something else then what code is asking for.
Improvement EZP-22191: Change $useAlwaysAvailable arguments in ContentService to true by default
Improvement EZP-22191: Change SearchService to pass languages & useAlwaysAvailable $fieldFilters to ContentService
Merge pull request #1016 from ezsystems/repository_respect_alwaysAvailable-EZP-22191

EZP-22191: As a User I expect API's with language filters to respect Always available flag
EZP-233278 Filesystem IO handler should create root if it doesn't exist
IO: Updated IOFactory to new Filesystem arguments
IO: Fixed prefix issue in filesystem
Merge pull request #1019 from ezsystems/EZP-23378-filesystem_root_folder

EZP-233278: Filesystem IO handler should create root if it doesn't exist
EZP-22280: Removed "image.delivery_url" setting as this is IO
responsibility
Fix EZP-22510: As a developer, I want to directly inject dynamic settings in my services

Before 5.4, if one wanted to implement a service needing siteaccess-aware settings (e.g. language settings),
they needed to inject the whole `ConfigResolver` (`ezpublish.config.resolver`) and get the needed settings from it.

This was not very convenient nor explicit.
Goal of this feature is to allow developers to inject these dynamic settings explicitly from their service definition (yml, xml, annotation...).

Static container parameters follows the `%<parameter_name>%` syntax in Symfony.

Dynamic parameters have the following: `$<parameter_name>[, <namespace>[, <scope>]]$`

Default namespace being `ezsettings`, and default scope being current siteaccess.

For more information, see [ConfigResolver documentation](https://confluence.ez.no/display/EZP/Configuration#Configuration-DynamicconfigurationwiththeConfigResolver).
EZP-22510: Ensure resettable services are reset on config scope change
EZP-22510: Support dynamic settings injection via setters
EZP-22510: Declared ezpublish.config.dynamic_setting.parser service
EZP-22510: Clarified properties names
EZP-22510: Fixed ConfigScopeListenerTest
EZP-22510: Added documentation note on DynamicSettingParser service

[ci skip]
EZP-25510: Fix doc
Fix EZP-23391: As a developer, I want to use dynamic setting with stylesheets/javascripts assetic tags

> https://jira.ez.no/browse/EZP-23391