Register Sentry's ErrorSubscriber for Rails 7.0+ apps

[st0012]

This implements the integration proposed in #1630.

After Rails 7.0, you'll be able to use the standardized Rails.error.record or Rails.error.handle interfaces to report exceptions to Sentry. Please check ActiveSupport::ErrorReporter for more information.

Gotcha & Workaround

If an operation is wrapped inside app.executor.wrap, any exception raised will be captured by Rails' error reporter,
even if it has been reported by either the SDK integration or user. So in some cases (e.g. ActionCable's channel actions), the same error could be reported twice.

I worked around this by marking if an exception has been captured by the SDK. And if it has, we don't capture it with the ErrorSubscriber.

(Dropping the original integration isn't an option because the contextual data may not be accessible from the error reporter)

Closes #1630

[codecov-commenter]

Codecov Report

Merging #1705 (af3d659) into master (4217838) will decrease coverage by 0.17%.
The diff coverage is 39.13%.

❗ Current head af3d659 differs from pull request most recent head 63225be. Consider uploading reports for the commit 63225be to get more accurate results

@@            Coverage Diff             @@
##           master    #1705      +/-   ##
==========================================
- Coverage   98.59%   98.41%   -0.18%     
==========================================
  Files         136      136              
  Lines        7808     7830      +22     
==========================================
+ Hits         7698     7706       +8     
- Misses        110      124      +14     

Impacted Files	Coverage Δ
sentry-rails/spec/sentry/rails_spec.rb	90.69% <25.00%> (-9.31%)	⬇️
sentry-rails/lib/sentry/rails/railtie.rb	97.26% <50.00%> (-2.74%)	⬇️
sentry-rails/spec/support/test_rails_app/app.rb	97.76% <100.00%> (+0.01%)	⬆️
sentry-ruby/lib/sentry/hub.rb	100.00% <100.00%> (ø)

---

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 4217838...63225be. Read the comment docs.

[st0012]

@georgeclaghorn I'd like to hear your opinion on the gotcha and the workaround I took 🙂

[georgeclaghorn]

I don't feel familiar enough with this gem to give a thorough review but this all seems reasonable to me. 👍

[sl0thentr0py]

cool that we support this now!

[casperisfine]

(Dropping the original integration isn't an option because the contextual data may not be accessible from the error reporter)

Could you expand on that? I'm not sure I follow.

[ariccio]

Interesting. I think this means I can turn on config.active_record.db_warnings_action, setting it to :report, and it will automatically send them through to sentry? Awesome! I'll have to try it!