Database changes can now actually be applied

There was no working way to apply a pending database change before shipping the code that depends on it, which recently caused an extended outage of publishing. There is now a single command that does it safely — it shows exactly what it would do before doing anything, names the database it is pointing at so it cannot be run against the wrong one, and applies everything at once or not at all.