fix: exponentialBackoffExpireAt should start at 0

[manofthepeace]

Fixes #1447

[codecov]

Codecov Report

Merging #1453 (33fba4f) into main (7408703) will decrease coverage by 0.18%.
Report is 3 commits behind head on main.
The diff coverage is 100.00%.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1453      +/-   ##
============================================
- Coverage     89.38%   89.21%   -0.18%     
+ Complexity     3367     3361       -6     
============================================
  Files           459      459              
  Lines         13402    13402              
  Branches       1641     1641              
============================================
- Hits          11980    11956      -24     
- Misses          792      814      +22     
- Partials        630      632       +2     

Files	Coverage Δ
...io/smallrye/mutiny/helpers/ExponentialBackoff.java	82.14% <100.00%> (ø)

... and 9 files with indirect coverage changes

[jponge]

Thank you!

Could you please add a test as well? UniOnFailureRetryTest is a good place for that.

[manofthepeace]

Hopefully the timing wont make it flaky. I tried with lower values but it made it flaky.

[jponge]

Looks like it worked in CI (great for catching flaky tests!) but you can always increase values if you think it's at risk for failing

[manofthepeace]

Seems ok with these values. Worse case the solution will be to bump the values with the rule that the initial wait needs to be under the expiry, and the subsequent backoff would be above.