[WIP] Implements a paged route collection using a paged route provider (2)

Current work, not done yet
when you say "give up" that would mean: Use either Paged collection *or* Lazy collection, but not a lazy paged collection, right?

i think having both would be a useful default. why not have an additional optional parameter for the default batch size? and if size < 1 do not use the paged collection? that would not feel too wrong to me. 

to change the default batch size, we would need to inject that into the DynamicRouter as its the place where the collection is created. we could also put the batch size into the provider interface and not pass it around, not sure which is more elegant (well, at least less inelegant)