chore: extend flaky until timestamp for grpc

[wantsui]

As part of #11274, the previous until timestamp for grpc was Oct 2024 which has already passed. Unless anyone knows about ipv6 support, this PR extends the timestamp until Jan 2025 to buy some more time.

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:

tests/contrib/grpc/test_grpc.py                                         @DataDog/apm-idm-python @DataDog/asm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: wantsui/extend-grpc-flaky-time
Commit report: c974f76
Test service: dd-trace-py

✅ 0 Failed, 607 Passed, 679 Skipped, 19m 2.07s Total duration (17m 45.06s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-11-14 15:37:52

Comparing candidate commit 0b75d5b in PR branch wantsui/extend-grpc-flaky-time with baseline commit ef58a6b in branch main.

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

[brettlangdon]

Future improvement, only skip this test in GitLab so it can still run locally, or if we moved it somewhere else it will start to run and pass again.

Not needed to make that change here, just documenting the idea for the future if we liked it.