route.start should warn when there is a data/route mismatch

[m-mujica]

In a sample app, I had the following routes:

route.register("/", { moduleId: "component-1" });
route.register("/component-2", { moduleId: "component-2" });

and the browser assets where located in a public folder...

when I loaded http://127.0.0.1:8080/public/ in the browser, can-route would redirect me to http://127.0.0.1:8080/ because of the route mismatch.

I was missing route.bindings.pushstate.root = "/public/", we could possibly warn the user that they might need to set the root property.

cc: @justinbmeyer