TaskBase - Do not sleep after success

[ygalblum]

The previous implementation got the status slept and then checked the status
Instead, get the status check it and sleep only if needed

[saimonation]

@ygalblum - is this mandatory? many of the background tasks falsely report "success" until the task actually begins. as a result, the code returns too early. I think all functions that "wait" must be tested to approve this PR

[ygalblum]

@saimonation
Doron is implementing a script that goes over a long list of paths and runs delete or undelete on them. According to him, the Portal should not have too many tasks running, so he added a wait after each operation. But, then we saw that it always waits for a second.

So, I looked into the implementation and saw that it was waiting needlessly because it first gets the status then waits then checks the status it got. So, it will always return a second after the task is completed. So, even if you are correct in your comment the code doesn't really compensate for it. In order to do that it should have waited before getting the status.

I tested it with the services.connect API and it worked.

If you think this is still an issue, I think we should fix the implementation here and wait before getting the status.
Then I will add an API for waiting for a list of tasks. This will allow Doron to start multiple tasks with one wait (this way the second's wait is not multiplied by the amount of tasks)