Honor RetryAfter

[marandaneto]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Honor Sentry RetryAfter.

💡 Motivation and Context

RetryAfter was implemented differently, per event, like the sentry-java SDK, but it's not honoring the unified API.

💚 How did you test it?

unit tests and manual tests.

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• All tests passing

🔮 Next steps

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@074eeac). Click here to learn what that means.
The diff coverage is 75%.

@@            Coverage Diff            @@
##             master     #236   +/-   ##
=========================================
  Coverage          ?   58.13%           
  Complexity        ?      574           
=========================================
  Files             ?       72           
  Lines             ?     2706           
  Branches          ?      237           
=========================================
  Hits              ?     1573           
  Misses            ?     1014           
  Partials          ?      119

Impacted Files	Coverage Δ	Complexity Δ
...n/java/io/sentry/core/transport/HttpTransport.java	59.75% <100%> (ø)	6 <0> (?)
...java/io/sentry/core/transport/AsyncConnection.java	60% <100%> (ø)	5 <0> (?)
...try/core/transport/RetryingThreadPoolExecutor.java	53.76% <50%> (ø)	13 <1> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 074eeac...0db7a24. Read the comment docs.