[🤖] Update Supported Versions

[TonyCTHsu]

This is a PR to update the table for supported integration versions.
Workflow run: Generate Supported Versions
This should be tied to tracer releases, or triggered manually.

[github-actions]

👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description.

If changes need to be present in CHANGELOG.md you can state it this way

**Change log entry**

Yes. A brief summary to be placed into the CHANGELOG.md

(possible answers Yes/Yep/Yeah)

Or you can opt out like that

**Change log entry**

None.

(possible answers No/Nope/None)

^{Visited at: 2024-12-19 19:58:39 UTC}

[datadog-datadog-prod-us1]

Datadog Report

Branch report: auto-generate/update-supported-versions
Commit report: 31fcc83
Test service: dd-trace-rb

❌ 1 Failed (0 Known Flaky), 21996 Passed, 1478 Skipped, 5m 33.34s Total Time

❌ Failed Tests (1)

• gem release process datadog.gemspec files includes all important files - rspec - Details

  Expand for error

   the missing elements were:      ["gem_output.json", "integration_versions.md"]
   
   Failure/Error:
     expect(gemspec.files)
       .to match_array(
         \`git ls-files -z\`
           .split("\x0")
           .reject { |f| f.match(directories_excluded) }
           .reject { |f| f.match(single_files_excluded) }
       )
   ...
  

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-07 21:51:46

Comparing candidate commit 31fcc83 in PR branch auto-generate/update-supported-versions with baseline commit d5f88ea in branch master.

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

scenario:profiler - hold / resume

• 🟥 throughput [-120080.413op/s; -118603.462op/s] or [-7.014%; -6.928%]

scenario:profiler - sample timeline=false

• 🟥 throughput [-0.619op/s; -0.609op/s] or [-9.534%; -9.378%]