New router

Like the `ScalaBusMod` this can be used as a replacement for `RouteMatcher`. It should be more idiomatic to use than the `RouteMatcher`.
This is purely subjective, but when defining methods like this, I like to focus the name on what they return. This is converting something to a Future. In the 2.0 prototype I created I just called this method `future`, see [here](https://github.com/galderz/next-vertx-scala/blob/master/src/main/scala/org/vertx/scala/FutureOps.scala#L7). I think it makes it easier to read it afterwards when it's being used.

Alternatively, since all these methods in this class convert stuff into Futures, you could have named the class `FutureOps` rather than the less clear `ScalaHelpers` which could have anything in it. I used a similar principle in [HandlerOps](https://github.com/galderz/next-vertx-scala/blob/master/src/main/scala/org/vertx/scala/HandlerOps.scala) class where I focus on creating implicit conversions of different stuff into Handler classes.