fix: add exponential backoff to spotify download

[SHA65536]

Adding exponential backoff for spotify client retries

Description

Adding exponential backoff for spotify client retries

Related Issue

#2461

Motivation and Context

Currently we do not wait at all between retries, leading to repeated 429 errors, reaching max retries, and risking ip bans.
Adding this exponential backoff will make sure we give time for the ratelimit to recover and avoid 429 errors.

How Has This Been Tested?

I have faced constant Max Retries, reason: too many 429 error responses errors when downloading a large playlist. Adding these 2 simple lines let me download the whole playlist in one go without any issues.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the CONTRIBUTING document
• I have added tests to cover my changes
• All new and existing tests passed

[luciesz1990-collab]

Adding exponential backoff for spotify client retries

Description

Adding exponential backoff for spotify client retries

Related Issue

#2461

Motivation and Context

Currently we do not wait at all between retries, leading to repeated 429 errors, reaching max retries, and risking ip bans.

Adding this exponential backoff will make sure we give time for the ratelimit to recover and avoid 429 errors.

How Has This Been Tested?

I have faced constant Max Retries, reason: too many 429 error responses errors when downloading a large playlist. Adding these 2 simple lines let me download the whole playlist in one go without any issues.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project

• My change requires a change to the documentation

• I have updated the documentation accordingly

• I have read the CONTRIBUTING document

• I have added tests to cover my changes

• All new and existing tests passed