[WIP] Refactored argument resolving out of the ControllerResolver

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | yes
| Deprecations? | yes
| Tests pass?   | yes
| Fixed tickets | #1547, #10710
| License       | MIT
| Doc PR        | tbd

Todo
===

 * [ ] Write docs
 * [ ] Make BC
 * [ ] Add priority
 * [ ] Review

BC
===

I've done my best to make this BC. It is now fully BC except from one case: If the logic in `ControllerResolver#getArguments()` is no longer used. If one would have used that method for custom argument resolving logic, it is no ignored. There should be a way that we can support both methods at the same time (in other words, create an argument resolver which uses the controller resolver).

Thanks
===

A huge thanks to @Iltar for giving me the idea and helping me setting up this PR.
SensioFrameworkExtraBundle, which did have this feature previously, used `supports`. We tried to stick as much as possible to the SensioFrameworkExtraBundle API, so the migration will be easy.