coordinating reducer version upgrades

[carlsverre]

Upgrading a reducer requires careful coordination between the server and the client.

Need to look at this from the perspective of client-server reducer version mismatch. When this occurs, the server is in a unique position to coordinate the upgrade.

The other problem is when the client submits mutations that were created by an older reducer version. This may require extending the reducer API to support "mutation migration" or lensing.