ci: use testrunner for microbenchmark build jobs

[brettlangdon]

LANGPLAT-716

We started having issues with the manylinux package image we were using since last week.

error: no Python 3.x interpreter found

There do not appear to have been any clear changes to the system causing this to happen, but switching to our testrunner image resolves the issue.

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:

.gitlab/benchmarks/microbenchmarks.yml                                  @DataDog/python-guild @DataDog/apm-core-python
.gitlab/benchmarks/steps/build-baseline.sh                              @DataDog/python-guild @DataDog/apm-core-python

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 280 ± 3 ms.

The average import time from base is: 280 ± 2 ms.

The import time difference between this PR and base is: 0.1 ± 0.1 ms.

The difference is not statistically significant (z = 0.79).

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.837 ms (0.65%)

ddtrace.bootstrap.sitecustomize 1.165 ms (0.42%)

ddtrace.bootstrap.preload 1.165 ms (0.42%)

ddtrace.internal.remoteconfig.client 0.620 ms (0.22%)

ddtrace 0.671 ms (0.24%)

ddtrace.internal._unpatched 0.030 ms (0.01%)

json 0.030 ms (0.01%)

json.decoder 0.030 ms (0.01%)

re 0.030 ms (0.01%)

enum 0.030 ms (0.01%)

types 0.030 ms (0.01%)

[brettlangdon]

This has been resolved by #14214