Azure: new VMs can be killed by other launchers

[SolomonShorser-OICR]

If a brand-new VM does not yet have a tag indicating which fleet it belongs to, a Reaper from a different fleet will kill it, thinking that this new VM is an orphan/failed deployment. The tag needs to be applied to the new VM ASAP in the process...

[SolomonShorser-OICR]

The DKFZ/EMBL launcher wrote this in its log when it killed a new BWA worker:

2015-10-23 18:22:16.268 [main] INFO  i.c.youxia.reaper.AzureHelper - bwa-fleet-670b699f-72b8-4369-9f0d-17326a78730a is missing state tag, likely an orphaned VM
2015-10-23 18:22:16.268 [main] INFO  io.cloudbindle.youxia.reaper.Reaper - bwa-fleet-670b699f-72b8-4369-9f0d-17326a78730a is added to kill list since it is an orphan