state: don't allow SetEnvironAgentVersion if state server upgrades are in progress

An upgrade isn't going to be able to complete if an upgradeInfo document for another upgrade is still active.
Are there any atomicity concerns here?  i.e. should the existing upgrade check be part of the transaction checks rather than before we run the transaction separately?