Move Environment locking from deployer to release-tools

Proposal

As part of a single coordinator pipeline move environment locking from deployer to release-tools

Responsibilities

This ensures that from the time we tell chef that it should stop installing the EE package on chef runs, to the time when we update chef with the new version of omnibus and re-enable intalls on chef runs, that no other deploys can happen on that environment.

Dependencies

• deployer

Notes from &154

I think this might make sense to stay in the deployer, or possibly use the feature in the product.

I think we were thinking that we might be able to use resource_groups for this, assuming a deploy is a single trigger from release-tools. When we start to have multiple jobs for a single environment in release-tools it might get more tricky.