Getting routing prototype into history
Revert "Getting routing prototype into history"

We're not using the prototype as a base, just want to to be in the history
so we can easily refer to it.

This reverts commit 4183bc98be89371c65f5a708b1f0ec351ccd6ffd.
Adding solution file
Updated build files.
Adding skeleton sample and test project
Initial mock up of key interfaces for routing.

This is heavily based right now on raw Owin as the request/response model
since that will work for building samples/tests, and doesn't require
ifdefs in the code for k10. Once it's feasible, I'll port this to use the
Microsoft.AspNet.Abstractions types.

The sample here includes some basic route/endpoint implementations just to
prove that the route engine works in naive scenarios. These might live on
in the future in some form, but for now it's just part of the sample.

The next step is to integrate this with WebFX and start developing the
integration/configuration story for WebFX.
change to non-static entrypoint, which klr is looking for
Added global.json
Updatng build.cmd to use cached NuGet.exe
integrating abstractions with routing
integrating abstractions with routing
cr feedback
Removing OwinRouteEndpoint
Workaround for myget being down.
Adding legacy rounting code - mostly unmodified to get it into history
removing datatokens/constraints/url-generation
updating OM of routing, about 10% better perf
CR feedback
Adding routebuilder
Adding optional parameters