retry on cloudflare timeout (#2695)

**Summary**
Some of the self hosted installations are hosted behind cloudflare. By
default, cloudflare proxy_write_timeout is set at 30s. If this timeout
is breached, Cloudflare responds with error with status code 524.
Currently this is treated as non retriable error by sentry-cli.


https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/

This PR ensures that sentry-cli retries on this timeout.

Co-authored-by: Manish Rawat <manish@Manishs-MacBook-Air.local>

Author: manishrawat1992

src/api/mod.rs

@@ -70,6 +70,7 @@ const RETRY_STATUS_CODES: &[u32] = &[
     http::HTTP_STATUS_503_SERVICE_UNAVAILABLE,
     http::HTTP_STATUS_504_GATEWAY_TIMEOUT,
     http::HTTP_STATUS_507_INSUFFICIENT_STORAGE,
+    http::HTTP_STATUS_524_CLOUDFLARE_TIMEOUT,
 ];
 
 /// Helper for the API access.

src/utils/http.rs

@@ -10,6 +10,7 @@ pub const HTTP_STATUS_502_BAD_GATEWAY: u32 = 502;
 pub const HTTP_STATUS_503_SERVICE_UNAVAILABLE: u32 = 503;
 pub const HTTP_STATUS_504_GATEWAY_TIMEOUT: u32 = 504;
 pub const HTTP_STATUS_507_INSUFFICIENT_STORAGE: u32 = 507;
+pub const HTTP_STATUS_524_CLOUDFLARE_TIMEOUT: u32 = 524;
 
 lazy_static! {
     static ref LINK_TOKEN_RE: Regex = Regex::new(