Express Routing enhancement

[Harper04]

Currently routing takes a naive express way approach.
First registered first served. Because we are registering by file listing our routing is defined by that order.

So we have no way to control / know which of the following routes will be executed:
/*
/api
or:
/api/todo/:id
/api/todo/list

i see two ways:

• adding a 'priority' number and sort by that

or:

• make express routing testable
• define a subset of valid path features (path params, wildcards at the end)
• maybe test for unreachable routes
• write a simple algorithm which determines the most specific route for conflicts and controls the order of the registration

[Aduril]

PR: #58