Unify Net::HTTP and Faraday implementations

[solnic]

Bonus refa after #2345

⚠️ this also fixes a bug that I found in Faraday instrumenter where it would early return nil if Sentry is not initialized instead of issuing a request. See 259f223

#skip-changelog

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.69%. Comparing base (09f348e) to head (04dde2d).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2360      +/-   ##
==========================================
+ Coverage   98.68%   98.69%   +0.01%     
==========================================
  Files         207      208       +1     
  Lines       13741    13748       +7     
==========================================
+ Hits        13560    13569       +9     
+ Misses        181      179       -2     

Components	Coverage Δ
sentry-ruby	99.05% <100.00%> (+0.01%)	⬆️
sentry-rails	97.41% <ø> (ø)
sentry-sidekiq	97.01% <ø> (ø)
sentry-resque	97.11% <ø> (+0.32%)	⬆️
sentry-delayed_job	98.92% <ø> (ø)
sentry-opentelemetry	100.00% <ø> (ø)

Files	Coverage Δ
sentry-ruby/lib/sentry/faraday.rb	100.00% <100.00%> (ø)
sentry-ruby/lib/sentry/net/http.rb	100.00% <100.00%> (ø)
sentry-ruby/lib/sentry/utils/http_tracing.rb	100.00% <100.00%> (ø)
sentry-ruby/spec/sentry/faraday_spec.rb	100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

[sl0thentr0py]

just one comment

[solnic]

@sl0thentr0py given that direct access to the configuration is not thread-safe, we could have a method for checking configuration values that would perform this additonal initialize? check, something like:

Sentry.configuration(:propagate_traces)

[sl0thentr0py]

feel free to to add a helper but the semantics of that (truthy or falsey?) are not always clean.

[sl0thentr0py]

ty!