Update supported versions workflow

[quinna-h]

What does this PR do?

Makes the following changes:

• Consolidate the logic from the generate_table_versions.rb script into the find_gem_version_bounds.rb script
• Update the description in the auto-generated PR body and in the generated markdown table to make the purpose of the file more clear

Motivation:

Addition to #4210

Change log entry
No.

Additional Notes:

How to test the change?
See the generated PR here: #4236

[github-actions]

Thank you for updating Change log entry section 👏

^{Visited at: 2025-01-29 14:55:57 UTC}

[datadog-datadog-prod-us1]

Datadog Report

Branch report: quinna.halim/update-supported-versions-script
Commit report: 17db220
Test service: dd-trace-rb

✅ 0 Failed, 22115 Passed, 1476 Skipped, 5m 16.66s Total Time
⌛ 4 Performance Regressions

⌛ Performance Regressions vs Default Branch (4)

• Rails integration tests for an application with a basic route behaves like appsec standalone billing with upstream appsec propagation without attack and trace is propagated as is from 2 sampling priority behaves like a request with propagated headers is expected to include "_dd.p.appsec=1" - rspec 4.43s (+3.79s, +592%) - Details
• Rails integration tests for an application with a basic route behaves like appsec standalone billing with upstream appsec propagation without attack and trace is propagated as is from 1 sampling priority behaves like a trace with ASM Standalone tags is expected to eq 1212121212121212121 - rspec 4.65s (+4s, +618%) - Details
• Rails integration tests for an application with a basic route behaves like appsec standalone billing with upstream appsec propagation without attack and trace is propagated as is from 2 sampling priority behaves like a trace sent to agent with Datadog-Client-Computed-Stats header is expected to equal true - rspec 3.68s (+3.05s, +485%) - Details
• Rails integration tests for an application with a basic route behaves like appsec standalone billing with upstream appsec propagation without attack and trace is propagated as is from 1 sampling priority behaves like a trace sent to agent with Datadog-Client-Computed-Stats header is expected to equal true - rspec 4.68s (+4.05s, +641%) - Details

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-29 20:19:56

Comparing candidate commit 17db220 in PR branch quinna.halim/update-supported-versions-script with baseline commit 38023b1 in branch master.

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

scenario:tracing - Propagation - Trace Context

• 🟥 throughput [-4461.349op/s; -4362.247op/s] or [-11.716%; -11.455%]

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.72%. Comparing base (04efab7) to head (81f1a59).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4326      +/-   ##
==========================================
- Coverage   97.72%   97.72%   -0.01%     
==========================================
  Files        1368     1368              
  Lines       82999    82998       -1     
  Branches     4220     4220              
==========================================
- Hits        81113    81107       -6     
- Misses       1886     1891       +5     

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

[marcotc]

Looks great!

[p-datadog]

Thank you!

[p-datadog]

Would be nice to see the generated markdown in this PR but if it's a lot of work I approve this PR as is and will review the markdown in a later PR.

[quinna-h]

@p-datadog Thanks! I saw that you approved it, but the PR with the generated markdown table is here: #4236

[bouwkast]

Thanks! Looks good to me

I think we'd want to follow up with product (specifically with httpx) and a follow up PR to add some tests for this.

trying to figure out merging issue