Update 429 retry-after response handling

[abraunegg]

• For every http perform action, check the response headers for any retry-after response

[abraunegg]

Without PR:

* Mark bundle as not supporting multiuse
< HTTP/1.1 429 Too Many Requests
< Retry-After: 150100
...
< Date: Sat, 27 Feb 2021 20:26:40 GMT
< Content-Length: 0
< 
* Connection #19 to host public.dm.files.1drv.com left intact

OneDrive returned a 'HTTP 429 - Too Many Requests' - gracefully handling error
[DEBUG] onedrive.downloadById(item.driveId, item.id, path, fileSize); generated a OneDriveException
[DEBUG] Handling a OneDrive HTTP 429 Response Code (Too Many Requests)
[DEBUG] Using Retry-After Value = 0
[DEBUG] HTTP Response Header retry-after value was 0 - Using a preconfigured default of: 120
Thread sleeping due to 'HTTP request returned status code 429' - The request has been throttled
Sleeping for 120 seconds

Even though the 429 is handled, the Retry-After: 150100 is being missed.

With PR:
Before OneDrive returned a 'HTTP 429 - Too Many Requests' - gracefully handling error is presented as log output, check the HTTP response headers each time a 429 is encountered, ensuring that if retry-after is present, the flag is correctly enabled & the correct value is used.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.