Optimize route lookup

[szuecs]

A Kubernetes cluster with routesrv enabled shows a data plane CPU profile of

proxy.do:

and proxy.lookupRoute:

and routing.matcher.match

So in total routing.matcher.match consumes >=99% of the whole proxy.do, which means we have an opportunity to optimize skipper_proxy metric our internal KPI.