write blog post on how schema migrations are smoother with Project:M36

After some discussion with @3noch, here are some improvements Project:M36's design brings to the table regarding schema migrations:

* branching allows painless migration testing even on a production server
* migrations can be reverted (often not possible with many types of SQL migrations)
* lock-free schema updates
* no null handling or column default changes
* greater room-for-error allows for greater confidence in results

In the future, it would be beneficial to implement built-in schema diffs and versioning. For example, there should be a client-side function which allows one to validate that expectation that the schema matches the client's expected schema.