Exception to the rule - Introducing DataStoreOperationException

Introducing a DataStoreOperationException to identify when a data store
related exception occurs during save/query from a DbContext. This allows
tooling, framework, etc. to handle issues related to database
operations.

Also updating the existing DbUpdateException to inherit from the new exception
type so that the existing cases where this is thrown don't need to be wrapped
in a new exception.
Fix for roslyn changes - part 1
Fix for roslyn changes - part 2
Added cloning to database model and methods needed to keep it up to date while the migration operations are processed.
Updating release Nuget.config
Refactoring value reader member binding into core query infrastructure.
Merge remote-tracking branch 'origin/release' into dev
Updating dev Nuget.config
Enables projection optimization for in-memory.
Fluent of the Navigator... (Initial implementation of fluent API for one-to-many relationships)

This is the basic initial implementation of the OneToMany method discussed in the last design meeting. It will create one or both nav props and then associate them with an FK, which is created if necessary.
Merge branch 'Fluent804' into dev
Enable shadow-property query via Property<T> extension method.
Code cleanup
Removing Redis FunctionalTests .csproj dependency on Redis-64 as it expects to find Redis-64.dll which does not exist. However do still want the Redis-64 package installed - so put the project.json file back but rename the test tool so that tests will contine not to run under K.
Adding logging support to relational update pipeline.
Adding support for schemas to the relational update pipeline
Adds support for Skip to relational query.
Becoming fluent in key foreign languages... (Implementation of ForeignKey on OneToMany)

Adds the ability to specify the foreign key in the fluent API when specifying 1:* relationships.
One, Two, Many... (Add ManyToOne API for configuring relationship from dependent end)

This is the equivalent API to OneToMany but for configuration of the relationship from the dependent end. It's primary use is to allow unidirectional relationships to be configured from the dependent end without needing specify the generic type and without needing to pass null for the missing nav property expression
Adds Min, Max, Sum support to relational query.