Concurrency with azmi

[maksiml2014]

azmi getblob/setblob shoud be an ataomic transaction.
If setblob fails halfway through, then the process should roll back and an old version of file should persist.
If getblob is called on a file that is currently being written by setblbob, then either getblob should wait or download the old version of the file. Either way, the behaviour shoud be documented in azmi.

[MangyCoyote]

Either blob lease or http header ETag should fix it.