…o the component (ogizanagi)This PR was merged into the 3.3 branch.Discussion----------[FrameworkBundle][Validator] Move the PSR-11 factory to the component| Q             | A| ------------- | ---| Branch?       | 3.3 <!-- see comment below -->| Bug fix?      | no| New feature?  | no <!-- don't forget updating src/**/CHANGELOG.md files -->| BC breaks?    | no| Deprecations? | yes <!-- don't forget updating UPGRADE-*.md files -->| Tests pass?   | yes| Fixed tickets |#22887 (comment) <!-- #-prefixed issue number(s), if any -->| License       | MIT| Doc PR        | N/AInstead of the 3 following deprecations: * The `ConstraintValidatorFactory::$validators` and `$container` properties   have been deprecated and will be removed in 4.0. * Extending `ConstraintValidatorFactory` is deprecated and won't be supported in 4.0.* Passing an array of validators or validator aliases as the second argument of   `ConstraintValidatorFactory::__construct()` is deprecated since 3.3 and will   be removed in 4.0. Use the service locator instead.I'd suggest simply deprecating the FrameworkBundle's class in favor of using a new `ContainerConstraintValidatorFactory`. To me, there is no reason anyone using the validator component without the framework bundle cannot use this PSR-11 compliant implementation, nor I see a reason to make it final.Commits-------68c1917 [FrameworkBundle][Validator] Move the PSR-11 factory to the component