feat: implement retry mechanism in image copy operation

[Azhovan]

This PR addresses this issue by refactoring the image copy logic with retry mechanism. following changes are made in this PR:

• Introduced retry strategies in image copy operation.
• Implemented limit and backoff with jitter strategies for retry attempts.

[Azhovan]

@tomponline @simondeziel
what do you think about this PR?

[MusicDin]

Thanks for your contribution. We will take a look at this ASAP

[Azhovan]

Thanks for your contribution. We will take a look at this ASAP

@MusicDin

I would like to highlight that this implementation does not resume the download from where it left off in the event of a failed attempt to download images from the server. This could lead to increased network traffic, as each new attempt starts from the beginning.

Implementing a feature to resume the previous operation would involve maintaining state and additional modifications to the current setup on both http client level and createImage() level

all that being said, if we are not fine with this compromise, we may go for a new solution

[simondeziel]

Thanks for working on this, this will paper over some image server hiccups like this failing after multiple minutes of downloading:

$ lxc launch ubuntu-daily:24.04 vn1 --vm
Creating vn1
Error: Failed instance creation: unexpected EOF

[simondeziel]

Suggested change

	// It Limits the retries to the number of URLs and spaces out with an increasing delay.
	// Retries is starting from 10 milliseconds and a jitter (random deviation) is added to the delay to prevent synchronized retries.
	// It limits the retries to the number of URLs and spaces out with an exponentially increasing delay.
	// Retries are starting from 10 milliseconds and a jitter (random deviation) is added to the delay to prevent synchronized retries.