Handle 429 (Rate limit exceeded) response gracefully
When the tests hit a rate limit, consider waiting for the amount of time specified in the response headers before proceeding.
A recent cleaning up on some throttling rules in: gitlab-com/gl-infra/k8s-workloads/gitlab-com!1239 (merged) caused the tests to hit rate limits on staging.
These are being added back and it was suggested that we should handle 429's gracefully in end-to-end tests.
Edited by Sanad Liaquat