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

[github-actions[bot]]

Backport 691604985643cf6ca74fa194f9b185b7e3ebd762 from #11368 to 2.16.

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.16 Commit report: 923fdac Test service: dd-trace-py

:white_check_mark: 0 Failed, 598 Passed, 688 Skipped, 19m 28.17s Total duration (15m 35.64s time saved)

[pr-commenter[bot]]

Benchmarks

Benchmark execution time: 2024-11-22 21:38:10

Comparing candidate commit 923fdac1c27aca4e46cc73210195e8109b5d87c0 in PR branch backport-11368-to-2.16 with baseline commit c5f71db23ecbeb841c2cf0115c0f41b879a0f7d5 in branch 2.16.

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