…for basic option resolving (webmozart)This PR was merged into the 2.6-dev branch.Discussion----------[OptionsResolver] Added a light-weight, low-level API for basic option resolving| Q             | A| ------------- | ---| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#11705| License       | MIT| Doc PR        |symfony/symfony-docs#4159See [the updated documentation](https://github.com/webmozart/symfony-docs/blob/issue11705/components/options_resolver.rst) for details on the usage of the simple API.The most important motivation for this change is DX and speed. The basic features of the component should be easily usable in a wide variety of use cases without impacting performance.For DX reasons, I added the static methods to the `Options` class, which makes the code concise and easy to read and understand:```phpuse Symfony\Component\OptionsResolver\Options;$options = Options::validateRequired($options, 'format');$options = Options::validateTypes($options, array(    'format' => array('string', 'int'),    'calendar' => 'int',));$options = Options::validateValues($options, array(    'calendar' => array(        \IntlDateFormatter::GREGORIAN,        \IntlDateFormatter::TRADITIONAL,    ),));$options = Options::resolve($options, array(    'format' => null,    'calendar' => \IntlDateFormatter::GREGORIAN,));```If you need to distribute the option configuration, this PR also extracts the configuration part of the `OptionsResolver` class into a new class `OptionsConfig`, which can be passed around. When the configuration is complete, pass the config object to `Options::resolve()` as second argument:```php$config = new OptionsConfig();$config->setDefaults(array(    'format' => \IntlDateFormatter::MEDIUM,    'calendar' => \IntlDateFormatter::GREGORIAN,));$options = Options::resolve($options, $config);```Consequently - since `OptionsResolver` extends `OptionsConfig` - the two following statements now become identical:```php$options = $resolver->resolve($options);$options = Options::resolve($options, $resolver);```Commits-------9066025 [OptionsResolver] Added a light-weight, low-level API for basic option resolving

…vel API for basic option resolving (webmozart)"This reverts commitaa59445, reversingchanges made tocc63edb.

…r (webmozart)This PR was merged into the 2.6-dev branch.Discussion----------[OptionsResolver] Merged Options class into OptionsResolver| Q             | A| ------------- | ---| Bug fix?      | yes| New feature?  | no| BC breaks?    | yes| Deprecations? | yes| Tests pass?   | yes| Fixed tickets |#4500,#9174,#10585,#10202,#11020, makes#7979+#10616 obsolete| License       | MIT| Doc PR        |symfony/symfony-docs#4159#11716 was reverted as preparation of this PR (453882c).The Options class was merged into OptionsResolver. This made it possible to fix several tickets, as indicated above.**Usage**See [the updated documentation](https://github.com/webmozart/symfony-docs/blob/issue11705/components/options_resolver.rst).**Bug Fixes**Previously, the options weren't validated before the normalizers were called. As a result, the normalizers had to perform validation again:```php$resolver->setAllowedTypes(array(    'choices' => 'array',));$resolver->setNormalizers(array(    'choices' => function (Options $options, $value) {         array_merge($options['choices'], ...);    },));// fatal error$resolver->resolve(array('choices' => 'foobar'));```This is fixed now.**BC Breaks**The `array` type hint was removed from `setRequired()`, `setAllowedValues()`, `addAllowedValues()`, `setAllowedTypes()` and `addAllowedTypes()`. If anybody implemented `OptionsResolverInterface`, they must adapt their code.The Options class was turned into an interface extending ArrayAccess and Countable. Anybody instantiating Options directly should instantiate OptionsResolver instead. Anybody using any of the methods available in Options (`get()`, `has()`) should use the ArrayAccess interface instead.Normalizers are not called anymore for undefined options (#9174). People need to set a default value if they want a normalizer to be executed independent of the options passed to `resolve()`.**Deprecations**OptionsResolverInterface was deprecated and will be removed in 3.0. OptionsResolver instances are not supposed to be shared between classes, hence an interface does not make sense.Several other methods were deprecated. See the CHANGELOG and UPGRADE-2.6 files for information.**Todo**- [x] Fix PHPDoc- [x] Adapt CHANGELOG/UPGRADE- [x] Adapt documentation- [x] Deprecate OptionsResolver[Interface]Commits-------642c119 [OptionsResolver] Merged Options class into OptionsResolver

…umentation to describe the 2.6 API (webmozart, peterrehm)This PR was merged into the master branch.Discussion----------[WCM][OptionsResolver] Adjusted the OptionsResolver documentation to describe the 2.6 API| Q             | A| ------------- | ---| Doc fix?      | no| New docs?     | yes (symfony/symfony#11716,symfony/symfony#12156)| Applies to    | 2.6+| Fixed tickets | -Commits-------575c320 Updated OptionsResolver documentation: removed static methodsfab825d Merge pull request#1 from peterrehm/patch-9f202fb8 Removed duplicate use statementsae66893 Added missing mailer class and use statements43ae1d8 [OptionsResolver] Adjusted the OptionsResolver documentation to describe the 2.6 API