[March customer interview] Remove the requirement for inserting sleep statements in scripts

Unfortunately, there are quite a few commands that return successfully, but have not completed processing in the background. This makes it difficult to write reliable scripts because of the need to insert sleep statements and hope for the best. It would be quite valuable to be able to assume a command has completely taken effect when a CLI command successfully returns.

App Service commands are a good example of where I need to put many sleep statements in my scripts, otherwise it just won't work reliably.

I am aware that this is ultimately caused by the behavior of the service API calls; not all calls designated as synchronous actually behave that way. However, there are already instances where Azure CLI abstracts away unfortunate service API behavior. As an Azure CLI user, I'm very happy with that because it results in more reliable scripts, that are also easier to write. And if this creates a feedback loop from the Azure CLI team back to the service API teams so that synchronous API calls will actually be synchronous, all the better. :)

So, the feature request is: please make sure that when an Azure CLI command successfully returns, all background processing has completed and the command has fully taken effect. Explicitly document instances where this isn't the case.