Implement EZP-22662: Implement core Public API configuration using Symfony container component

This PR resolves issue https://jira.ez.no/browse/EZP-22662

Partially extracted from https://github.com/ezsystems/ezpublish-kernel/pull/792

This implements Symfony container component based service container for Public API and moves PAPI configuration to `Core/settings`. With this we finally run PAPI integration tests on "live" configuration.

**Note that this split did not introduce any changes for the users.**

On top of core PAPI configuration our Symfony application uses different/additional slots, IO services and FieldType services. For this reason FieldType services are extracted from `fieldtypes.yml` and are not shared. Slots and IO services were already separate.

External storage handlers are also extracted from `fieldtypes.yml` as the size of the configuration there started becoming hard to maintain.

Because PAPI can't be aware of the location and organization of the application using it, to enable sharing of configuration files like character transformation rules and XML schemas new parameter is introduced, pointing to PAPI root directory:

```yaml
parameters:
    ezpublish.kernel.root_dir: %kernel.root_dir%/../vendor/ezsystems/ezpublish-kernel
```

#### Service container

New service container with caching support based on Symfony container component is implemented, old service container with settings is removed. Integration tests setup factories, `container.php`, `bootstrap.php` and `config.php` are updated for the new container.

#### Configuration overrides

Our Symfony app has Doctrine connection available by Doctrine bundle. This is not the case in core PAPI, so separate connection service is defined there which is overridden in Symfony app by factory. This service creates database connection through new static factory method `Persistence/Doctrine/ConnectionHandler::createConnectionFromDSN()`.

#### Tests

Integration tests are adapted to run on a new container. FieldType SPI integration tests changes made in https://github.com/ezsystems/ezpublish-kernel/pull/825 are here reverted and it is again possible to create custom storage handler.

Separate YAML configuration files for integration tests are added, making override for each suite simple.

### Additional

* PR https://github.com/ezsystems/ezpublish-kernel/pull/825 introduced `*.common` tags for criterion and search clause handlers common to Content and Location search. As it is possible to define multiple tags on a service, this was not necessary and is here removed.

* Removed deprecated parameter `ezpublish.fieldType.ezrichtext.embed.rendering_strategy`, a leftover from https://github.com/ezsystems/ezpublish-kernel/pull/758

### TODOs

- [x] rebase on changes from ISBN field type: https://github.com/ezsystems/ezpublish-kernel/pull/852