Deploying a new revisions causes a mismatched in the proxy revisions deployed

Steps to reproduce (using the tool):

1. Create a new proxy
2. Download the revision to your local machine
3. Deploy a new revision to the proxy
4. Undeploy your newly created revision 2.
5. Revision 1 will still be active on at least 1 MP.

If you add a step, to undeploy the proxy first then deploy the next revision I think that works around the issue. I believe this issue stems from this feature:
Deploys an API proxy to Apigee Edge. If the proxy is currently deployed, it will be undeployed first, and the newly deployed proxy's revision number is incremented.

Here I think the app is not waiting long enough to deploy the next revision after undeploying the first one causing a mismatch of revisions on the MPs.

This is using the latest version of the tool (.90) with nodejs version 8.11.0.

I can only seem to reproduce this issue with this tool.

Reproduce the deployment sequence with apigeetool .90 and Node.js 8.11.0: create a proxy, download a revision, deploy a new revision, then undeploy it and inspect the revisions active on each MP. Start by tracing the deploy path that undeploys an existing proxy before deploying the next revision; done means the proxy has consistent revisions across MPs without requiring a separate manual undeploy.