[RFC] Access control in route configuration listener

[Nek-]

For CRUD routes we can specify an access control directly in the route. This is a nice feature that the user may want to use more globally in its application.

Using a listener for that have 2 interesting points:

• It removes the check from the controller (or partially)
• It makes it available to use for any route

This is not something definitive. Just an idea, maybe it's totally invalid. It needs to be test.

This came to me because while using API Platform, some users are defining routes against models just for having their routes in documentation (with a result of broken doc) but also with access control.

In facts, maybe the security.yaml file is a better place and there's no reason to change that. (probably)

I'm just writing some idea here.