Atomic Schema Upgrade for HMS

Currently, as schematool applies schema changes during an upgrade, each change is autocommitted. So if it fails after applying a few changes from an upgrade file, those changes remain in the schema. So re-running the schematool fails at the first line because that change already exists.

Instead, we should create a transactional boundary between each upgrade file, aka commit only after all the changes in an upgrade file are successful.