chore(yaaredis): remove yaaredis support

[mabdinur]

yaaredis is deprecated, we shouldn't support it

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

releasenotes/notes/remove-yaaredis-095441532392e12f.yaml                @DataDog/apm-python
ddtrace/_monkey.py                                                      @DataDog/apm-core-python
docs/index.rst                                                          @DataDog/python-guild
docs/integrations.rst                                                   @DataDog/python-guild
docs/spelling_wordlist.txt                                              @DataDog/python-guild
lib-injection/sources/min_compatible_versions.csv                       @DataDog/apm-core-python
min_compatible_versions.csv                                             @DataDog/apm-core-python
riotfile.py                                                             @DataDog/apm-python
supported_versions_output.json                                          @DataDog/apm-core-python
supported_versions_table.csv                                            @DataDog/apm-core-python
tests/contrib/suitespec.yml                                             @DataDog/apm-core-python @DataDog/apm-idm-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-06 21:40:59

Comparing candidate commit 1eb7cc4 in PR branch munir/remove-unwanted-warnings with baseline commit 1247ac2 in branch main.

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

[emmettbutler]

What changed since 025c020?

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: munir/remove-unwanted-warnings
Commit report: 1eb7cc4
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1184 Skipped, 3m 35.01s Total duration (25m 19.78s time saved)

[mabdinur]

What changed since 025c020?

Ahhh I missed this. I just went off the deprecation warning. I'll remove the whole integration.

[github-actions]

The backport to 2.21 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.21 2.21
# Navigate to the new working tree
cd .worktrees/backport-2.21
# Create a new branch
git switch --create backport-12226-to-2.21
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6a06f77b338ee3929cf3bbc9237fe76175e0a001
# Push it to GitHub
git push --set-upstream origin backport-12226-to-2.21
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.21

Then, create a pull request where the base branch is 2.21 and the compare/head branch is backport-12226-to-2.21.

[erikayasuda]

Note to future self: We are going to revert this from main since it unfortunately missed getting backported to 3.0 during the 2.x -> 3.x migration. It's already behind a deprecation flag, so it should be removed completely in 4.0 when we do the 3.x -> 4.x migration next year.