chore(ci): add retry to the run test step for circleci [backport 2.15]

[github-actions[bot]]

Backport 691604985643cf6ca74fa194f9b185b7e3ebd762 from #11368 to 2.15.

Some CircleCI tests are flaky, which causes merge queue times to be long if the PR gets ejected for flakes. This will hopefully help remedy this symptom. Flakes should still be recorded since the same test will fail on the same commit, it just won't be a hard blocker if a retry will make the test pass.

Checklist

• [x] 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

• [x] 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

[datadog-dd-trace-py-rkomorn[bot]]

Datadog Report

Branch report: backport-11368-to-2.15 Commit report: 9ae44f6 Test service: dd-trace-py

:white_check_mark: 0 Failed, 592 Passed, 694 Skipped, 19m 34.67s Total duration (15m 21.62s time saved)

[pr-commenter[bot]]

Benchmarks

Benchmark execution time: 2024-11-22 21:37:00

Comparing candidate commit 9ae44f6c3962bde3aca250cd6eb8fd5aaeacdc7f in PR branch backport-11368-to-2.15 with baseline commit b7563444c0c7b03ac1206ed2aebfc1d885eb1c11 in branch 2.15.

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