Use attempt_threshold to skip reporting on first N attempts

[benhutton]

This is an implementation for #1632.

I am bringing over the concept of attempt_threshold from Honeybadger.

Retry counting is a bit tricky, and so I included a comment based on a GH comment from Honeybadger.

There are two relatively arbitrary decisions I made here that you should validate:

1. I am 1-indexing attempts, not 0-indexing
2. I am skipping until the number of attempts equals the attempt_threshold. Alternatively, we could skip until number of attempts is greater than attempt_threshold.

Thanks for your consideration!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.20%. Comparing base (d8c1066) to head (97f9969).
Report is 9 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2503   +/-   ##
=======================================
  Coverage   98.19%   98.20%           
=======================================
  Files         128      128           
  Lines        4833     4843   +10     
=======================================
+ Hits         4746     4756   +10     
  Misses         87       87           

Components	Coverage Δ
sentry-ruby	98.57% <ø> (+<0.01%)	⬆️
sentry-rails	97.07% <ø> (ø)
sentry-sidekiq	97.48% <100.00%> (+0.06%)	⬆️
sentry-resque	92.85% <ø> (ø)
sentry-delayed_job	95.65% <ø> (ø)
sentry-opentelemetry	99.31% <ø> (ø)

Files with missing lines	Coverage Δ
sentry-sidekiq/lib/sentry/sidekiq/error_handler.rb	97.22% <100.00%> (+0.55%)	⬆️

... and 1 file with indirect coverage changes

[solnic]

Thank you, this LGTM. Could you update the CHANGELOG.md (top level one) too so that we can get a green build?