WIP: Instance Based FrameworkProvider

## Support web frameworks that run in "self-hosted" modes such as [WebAPI](http://www.asp.net/web-api) and [NancyFx](http://nancyfx.org/) as well as [OWIN](http://owin.org/).

> This thread was originally a issue and was [converted to a pull request](http://issue2pr.herokuapp.com/)

When building out infrastructure support for WebAPI, it looks like we might have found a problem with the design. It would appear that the design of how IFrameworkProvider is used, it assumes that you have access to a static context (like HttpContext.Current). 

To clarify, its not IFrameworkProvider itself, but by way of the IGlimpseConfiguration. By default, IGlimpseConfiguration contains a single instance of IFrameworkProvider that will be used throughout the lifetime of the appdomain. It could be possible to inject different IFrameworkProvider here for each request, but since IGlimpseConfiguration is shared between requests, this probably wouldn't work.

Hence, it we need like we need a way to have IFrameworkProvider's created on an request by request basis, to be passed through the runtime.