motivation:
As we move towards a full route-based system, we need to handle access based on route and parameters rather than tying ourselves in knots reconstructing system paths.
The method we are looking to add should take a route name, an array of parameters, and maybe an optional request objects (defaults to the current one in the DIC) - it would then find the route and load any objects needed before passing off to the actual access checks.
For some use cases, this depends on:
#2031487: When replacing the upcasted values in the request attributes array, retain the original raw value too
