Fix matching the route

[onmyway133]

• This add shuffle to the tests for route. So we're sure that order does not matter
• Remove optional route (aka components count does not match)

Example: we have 2 routes

a:b:{c}
a:b

and a urn a:b, then what route should we match?

Removing optional arguments makes it explicit to declare the route by always matching the number of components

• Check concrete and wildcard match count (aka components count matches, but we have overlap because of wildcard)

Example: we have 3 routes

a:b:c
a:b:{c}
a:{b}:{c}

and a urn a:b:c, then we should select route a:b:c

This is rare, actually

[zenangst]

@onmyway133 this is very interesting! Great job with the improvements. 😎