Monster cleaning service... (A bit of cleanup in MonsterContext`.cs)

Combines the two sections of fluent API calls into one.
Refactoring ModificationCommandBatch to improve extensibility
Remove exception wrapping from query compilation
Adding unit tests for Redis Query classes
Updated the migration tool to work with K10, including core CLR:

1. ifdef-ed code from EntityFramework.Design assembly that don't compile with core CLR.
2. Replace Assembly.LoadFile with Assembly.Load and removed the References option.
3. Replace all variable names like assemblyFile with assemblyRef.
4. Using PathResolver to resolve relative paths instead of GetCurrentDirectory.
5. Updated code DbContextConfigurationExtensions.GetMigrationNamespace to cover the case of empty context namespace.
6. Updated tests.
Blue Screen of Curable Illness

Initial cut of middleware to provide a custom error page when a database exception occurs in an ASP.NET vNext. The error page is displayed when there is some action that can be taken with migrations that may fix the error (applying migrations, scaffolding a new migration, etc.). If the action is just applying the existing migrations then we also include the ability to apply them from the page. This makes use of another piece of middleware that can apply migrations.

This functionality will only ever be enabled in local dev mode by default (same as other diagnostics pages for ASP.NET vNext).

This is just an initial cut, things that still need to happen are:
 - Better error handling/validation in middleware
 - Tests
 - Handling context not being registered in DI
 - Styling for error page (currently it just has very simple styling largely copied from the existing ASP.NET vNext error page)