[Feat] Add queue mechanism to handle rate limit errors in Wayback Machine auto-save feature

[ramazansancar]

Add a queue mechanism to store requests in the Browser Storage area and handle rate limit errors in the Wayback Machine auto-save feature. Fixes #1048

• Add a queue mechanism to store requests in the Browser Storage area when the auto-save feature is turned on.
• Implement rate limit error handling to calculate the nearest request time and remain in standby mode until the rate limit is reset.
• Add functionality to retry requests from the queue after encountering rate limit errors.
• Update the savePageNow function to add requests to the queue and handle rate limit errors.
• Process the queue when the browser starts up.
• Remove the request from the queue when the operation is successful.

[ramazansancar]

I am open to suggestions for the RATE_LIMIT_AND_SERVER_ERROR_CODES field. If there is any HTTP code that needs to be added or removed, you can specify it.

[cgorringe]

Thanks, I will take a look sometime after we get our servers back online.

[ramazansancar]

Hello, when will the Save Page Now feature be available again on an API basis for the development to be published? @cgorringe

[cgorringe]

@ramazansancar Save Page Now is partially back up but may still encounter some slowness. I've got a lot going on right now so will likely not get to testing this for a bit still.

[ramazansancar]

Any progress on this place? @cgorringe

And as an additional feature, I plan to create a queued requests page. How about this? If someone accidentally gets into the queue, they can delete them and fix the problem.

Sample draft :D

[ramazansancar]

Is there any progress? @cgorringe

[ramazansancar]

Is there any progress? @vbanos