Add byebug to MRI gemfiles

[p-datadog]

What does this PR do?
Adds byebug to all of the MRI gemfiles.

Motivation:
I use byebug for debugging.

Change log entry
None

Additional Notes:

How to test the change?

[datadog-datadog-prod-us1]

Datadog Report

Branch report: byebug
Commit report: 3252241
Test service: dd-trace-rb

✅ 0 Failed, 22024 Passed, 1458 Skipped, 5m 28.42s Total Time

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.75%. Comparing base (7f079c9) to head (3252241).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4188      +/-   ##
==========================================
- Coverage   97.75%   97.75%   -0.01%     
==========================================
  Files        1357     1357              
  Lines       81890    81890              
  Branches     4164     4164              
==========================================
- Hits        80054    80053       -1     
- Misses       1836     1837       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-03 21:44:49

Comparing candidate commit 3252241 in PR branch byebug with baseline commit 7f079c9 in branch master.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 30 metrics, 2 unstable metrics.

scenario:profiler - sample timeline=false

• 🟩 throughput [+0.602op/s; +0.610op/s] or [+10.223%; +10.357%]

[ivoanjo]

👍 LGTM. I think we've been discussing and exploring a bit the tension between having very minimalistic images for CI vs having tools for development.

I'm not sure we've settled on a balance yet, and I think having byebug be quickly available on short notice seems like a reasonable thing to do.

[p-datadog]

I have been trying binding.b for the last couple of days and it seems to work so far, I will continue testing it and perhaps this PR is not needed.