Create a function for listing all possible routes

[KidkArolis]

(leaf routes with their patterns)

[KidkArolis]

Actually, router already exposes a variable called matchers which contains all routes with names, paths and even individual .. routes that make up the .. route (man, I feel we're missing a word to describe the individual route node - ah nodes!?)

I could rename matchers -> routes and then it could have routes.routes -> routes.nodes.

Basically, we could call the individual bits .. nodes instead of routes. And call the entire thing a route.

[KidkArolis]

Or from express 4 - we could continue calling individual things routes (since that's already part of a lot of API, e.g. transition.routes) and instead rename matchers to stack..

Actually, probably it's best as is now..

[KidkArolis]

Solved by #108