Some times issue duplication happens upon nearing the rate limit

[mskd12]

Suppose an issue is created and then the rate limit is also reached. In this case, we will not be able to know the status of the issue migration. This means a timeout occurs in the inner retry loop. Since the outer loop performs indefinite retry, another issue is created after the rate limit is refreshed.

A possible solution is to do indefinite retry in the inner retry loop also. This way we will break out of it only in case we throw some errors.

Although we are probably done using JIM, I just wanted to write out something I noticed.