Breakup dependencies, e.g. with Configuration #97
Description
Currently Options depends on Configuration because of the serviceCollection.Configure(configuration)
overload.
This means that any package that indirectly depend on Options also depend on Configuration, e.g. Entity Framework 7 depends on Caching which depends on Options which depends on Configuration, therefore even if we made the explicit decision not to couple Entity Framework with Configuration, the dependency exists and is carried even to places where it isn't commonly used, e.g. desktop .NET or Windows UAP applications.
The dependency could be broken by splitting the parts of options that depend from configuration (e.g. serviceCollection.Configure(configuration) and its implementation class
ConfigureFromConfigurationOptions`) into their own package.
Optionally, moving that package in its own repo would help breakup the chain of build dependencies for our CI.