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.
Added a SqlServerMigrationOperationPreProcessor class that is used to pre-process the migration operations (alter column and drop column) before generating SQL. A drop column is pre-processed into a DropDefaultConstraintOperation if a default exists followed by the DropColumnOperation. Alter columns are preceded/succeeded by corresponding Drop/Add default constraint, primary key, foreign key, index. The preceding/succeeding operations are inserted before/after groups of alter column operations. Alter timestamp column is pre-processed into drop/add column.

Changed IMigrationOperationVisitor from interface to abstract class to be able to provide a default implementation.
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)
Refactoring of result operator handling to support composition and improve perf.
Adds Last translation to relational query
Fixes relational order-by client eval
Parameterize top/offset/limit queries
Wot no key? (Allow principal/dependent to be flipped by specifying FK type only)

Allows the ForeignKey API to be used without any parameters to specify/flip the principal and dependent while the FK property itself is still discovered by convention.
7th Amendment - The jury rules v7.0.0 with no RTM
Adding version to Microsoft.AspNet.Diagnostics.Entity so that it's consistent with existing EF packages
Also adding warningsAsErrors to be consistent with other packages
How many times cam I mention Z'ha'dum? (Added tests for shadow state FKs)

We already had functional coverage for this in Monster Model, but I realized we were missing more direct testing with specific verification of model changes.
Renamed Migrator to DbMigrator.
"He told me you killed my PK!" "No, I am your PK" (Added ReferencedKey API to allow specification of non-primary principal key)

This is the counterpoint to the ForeignKey API and is used to specify the key properties at the principal end of the relationship.

Note that Migrations doesn't support yet creating the required candidate keys so functional testing is limited to in-memory. Also, we decided this morning to remove the parameterless overloads of ForeignKey amd ReferencedKey, but I will do that as a separate change.
That name no longer has any meaning for me... (Remove parameterless overloads of ForeignKey and ReferencedKey)

After discussion of this API we decided that the semantics of these overloads were ambiguous as to whether they were for just specifying the end or indicating that the FK should be created explicitly in shadow state. Also, it was not super-clear which was the principal/dependent when no property was supplied. Given that the only real value is to avoid having to be explicit about either the FK or PK in cases where the principal/dependent need to be flipped, we decided it was better to remove these overloads.
Removed sources from project file
Merge branch 'dev' of github.com:aspnet/EntityFramework into dev
Quicker, easier, more seductive... (Change DbContext.OnModelCreating to get a ConventionModelBuilder)

The relationship fluent API patterns we have introduced cannot work without some conventions. However, we feel that there is still value in having a ModelBuilder API that is very close to the metadata model and never uses any conventions. Therefore, the plan is to move the new relationship API into the ConventionModelBuilder. Since we want this API to be the one available in OnModelCreating this means that the parameter in OnModelCreating should now be ConventionModelBuilder.

Also did the rename of the parameter per issue #441.