[FrameworkBundle] Improved controller class error

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | https://github.com/symfony/symfony/issues/11304
| License       | MIT
| Doc PR        | 
I'm mixed on this. I *do* like having the route available later - I think this helps a lot. So I *do* want that feature. But, it does feel a little weird passing the `$route` around (especially in the component, where you could follow a completely different standard for where you store your route (e.g. not `_route`). The `_route` comes from the Routing component, which you might not be using.

Anyone have any thoughts on this? Is this possible? Or do we need to *not* use the route name? It's an odd situation where the component class actually needs to help us a little bit, otherwise we don't have access to what we need in the FrameworkBundle version of `ControllerResolver`.