[1139735] HA upgrade issues with storage cluster schema change
Revert the flawed db-upgrade logic. We can't update all existing rows in
the server and storage_node tables, only the one being upgraded can be set
to the current version. But this is unknown to the upgrade logic.  Instead
create the new column on the fly during the first upgrade that wants to
set it.  Set all rows to an "old" version, and then update only the one row
that reflects the upgrade in progress.  This also has the benefit of
restriction on upgrade ordering.