Fix race condition in DynamicallyProvisionedDeletePodTest

[dkoshkin]

Test:

[ebs-csi-e2e] [single-az] Dynamic Provisioning should create a deployment object, write and read to it, delete the pod and write and read to it again

Is this a bug fix or adding new feature?
bug fix

What is this PR about? / Why do we need it?
Waif for pod to be actually deleted before checking if the replacement pod is running.

Test snipped from a failed test:

STEP: deleting the pod for deployment
Feb  7 17:46:15.467: INFO: Deleting pod "ebs-volume-tester-rp8kv-58f768d56f-fvwx5" in namespace "e2e-tests-ebs-zm5g2"
STEP: checking again that the pod is running
STEP: checking pod exec
Feb  7 17:46:15.822: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/Users/dkoshkin/.kube/config exec ebs-volume-tester-rp8kv-58f768d56f-fvwx5 --namespace=e2e-tests-ebs-zm5g2 -- cat /mnt/test-1/data'
Feb  7 17:46:17.222: INFO: stderr: ""
Feb  7 17:46:17.222: INFO: stdout: "hello world\n"
Feb  7 17:46:19.226: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/Users/dkoshkin/.kube/config exec ebs-volume-tester-rp8kv-58f768d56f-fvwx5 --namespace=e2e-tests-ebs-zm5g2 -- cat /mnt/test-1/data'
Feb  7 17:46:20.599: INFO: stderr: ""
Feb  7 17:46:20.600: INFO: stdout: "hello world\n"
Feb  7 17:46:22.603: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/Users/dkoshkin/.kube/config exec ebs-volume-tester-rp8kv-58f768d56f-fvwx5 --namespace=e2e-tests-ebs-zm5g2 -- cat /mnt/test-1/data'
Feb  7 17:46:23.975: INFO: stderr: ""
Feb  7 17:46:23.975: INFO: stdout: "hello world\n"
Feb  7 17:46:25.977: INFO: Unexpected error occurred: Failed to find "hello world
hello world
", last result: "hello world
"
...
Feb  7 17:47:10.705: INFO: At 2019-02-07 17:46:15 -0500 EST - event for ebs-volume-tester-rp8kv-58f768d56f: {replicaset-controller } SuccessfulCreate: Created pod: ebs-volume-tester-rp8kv-58f768d56f-nbn6r
Feb  7 17:47:10.706: INFO: At 2019-02-07 17:46:15 -0500 EST - event for ebs-volume-tester-rp8kv-58f768d56f-nbn6r: {attachdetach-controller } FailedAttachVolume: Multi-Attach error for volume "pvc-1cf68f73-2b2a-11e9-bcab-7a58f389f9e0" Volume is already used by pod(s) ebs-volume-tester-rp8kv-58f768d56f-fvwx5

ebs-volume-tester-rp8kv-58f768d56f-fvwx5 is the original pod is being deleted, because the test didn't wait for the pod to be fully deleted the test checks that pod instead of the new pod ebs-volume-tester-rp8kv-58f768d56f-nbn6r

What testing is done?
Local testing

[coveralls]

Pull Request Test Coverage Report for Build 418

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 64.433%

---

Totals
Change from base Build 417:	0.0%
Covered Lines:	779
Relevant Lines:	1209

---

💛 - Coveralls

[dkoshkin]

/retest

[leakingtapan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkoshkin, leakingtapan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [leakingtapan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment