Fix EZP-23163: Use the new ConfigurationProcessor in kernel

> https://jira.ez.no/browse/EZP-23163

This PR *migrates* current configuration parsers for EzPublishCoreBundle to use the new `ConfigurationProcessor` and `Contextualizer` (see #931).

Parsers are now *stored* in a main `ConfigParser` which acts as a proxy and is passed to the `ConfigurationProcessor`.

## TODO
* [x] Implement new main configuration parser
* [x] Change implementation for all existing configuration parsers
* [x] Implement new ConfigurationProcessor in LegacyBundle
No, since it's not the same context. `mapConfig()` is called in a loop of available scopes, so calling `preMap()` here is pointless as we want to call it *before* this loop (same for `postMap()`).
Besides there is absolutely no difference.