feat: implement exponential retry mechanism for handling network errors

[1abhishekpandey]

Description

• This PR removes the existing retry mechanism for network errors and replaces it with an exponential retry mechanism with jitter. Now, retries will occur exponentially for every 4xx and 5xx status code (except 400 and 404). If the network is unavailable, retries will continue with a one-second delay.
• The maximum limit is 5 minutes; once this limit is reached, the retry process will start over from the beginning.
• Example sequence:

5sec, 7sec, 22 sec, 42 sec, 56 sec, 3 min 11 sec, 5 min 0 sec,
3 sec

NOTE: No event is deleted in this process.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• Version upgraded (project, README, gradle, podspec etc)
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added unit tests for the code
• I have made corresponding changes to the documentation

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud