Removing RouteContext.RequestPath and calculating it from HttpContext as needed

Apparently PathString.Value can be null. This seemed like an obvious scenario where you could throw a NullRef but there might be other places you might want to account for it.