EFor 429 errors, do you consider adding a setting or change the default behaviour to allow retries?
From what I have seen, when there is a 429 error (rate limit), Crawlee tries rotating the session, but if all of the sessions it uses return 429 (for example all proxies have been rate-limited) the request is just marked as handled and forgotten. I would expect this to be considered a transient error that can be fixed with time, same as a 500 error. Do you expect to support this change in behaviour in the future?
