Specifying a custom EndpointCounterKeyBuilder per route

[Phil-G]

I have a route that needs special handling. Something like GET /User/{userId}/Info
I want the route to have a limit, regardless of the IP or client ID. GET /User/1/Info should be tracked separately from GET /User/2/Info

It would be helpful to have more config granularity per route to prevent endpoints from getting overloaded and taxing the DB.