feat(ci_visibility): make pytest v2 plugin the default version

[vitor-de-araujo]

Previously, the pytest v2 plugin was disabled by default, and could be enabled by setting the DD_PYTEST_USE_NEW_PLUGIN_BETA variable to true. In ddtrace 3.0, the pytest v2 plugin will be enabled by default, and DD_PYTEST_USE_NEW_PLUGIN_BETA will not be used anymore.

For now I'm not removing the code for the old plugin version. Instead, I'm adding an internal environment variable _DD_PYTEST_USE_LEGACY_PLUGIN that allows running pytest with the old plugin, and using that in the tests that depend on it. We can remove the code (and the variable) after the 3.x release, since this is not part of the public interface.

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/ci_visibility-feat-pytest-v2-default-db160906c0ba26dc.yaml  @DataDog/apm-python
.gitlab/tests.yml                                                       @DataDog/python-guild @DataDog/apm-core-python
ddtrace/contrib/internal/pytest/_plugin_v1.py                           @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/pytest/_utils.py                               @DataDog/apm-core-python @DataDog/apm-idm-python
docs/configuration.rst                                                  @DataDog/python-guild
hatch.toml                                                              @DataDog/python-guild
riotfile.py                                                             @DataDog/apm-python
tests/contrib/flask/test_appsec_flask_pytest_iast_no_snapshot.py        @DataDog/asm-python
tests/contrib/pytest/test_pytest_snapshot.py                            @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest_snapshot_v2.py                         @DataDog/ci-app-libraries
tests/contrib/selenium/test_selenium_chrome.py                          @DataDog/ci-app-libraries

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: vitor-de-araujo/SDTEST-1210/pytest-v2-default
Commit report: 4d60ace
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1468 Skipped, 4m 57.93s Total duration (35m 44.53s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-03 11:28:45

Comparing candidate commit 4d60ace in PR branch vitor-de-araujo/SDTEST-1210/pytest-v2-default with baseline commit 7257296 in branch 3.x-staging.

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