Refactor retry logic for deployment key

[samyfodil]

Sometimes, a build might be triggered before the repository is registered, which mean a deployment key was added. For these reason we have a retry logic here https://github.com/taubyte/tau/blob/main/protocols/monkey/job.go#L88. Frankly, this code does not look good.

I suggest moving the check for deployment key to https://github.com/taubyte/tau/blob/main/protocols/monkey/job.go#L41, and use a helper function that will retry for a number of times till we get repo with a deployment key.

[mortum5]

How much Attempts and Delay do we need? Also can you describe it in more detail. Because i dont understand what workflow of logic should be followed.

[samyfodil]

You can have the retry and wait as global variables

In L41 we fetch repo info. we should re-try there if no key is found. then move on with the logic.
Re-fetching in L81 is not necessary