chore: use guess-next-dev instead of release-branch-semver [3.4]

[erikayasuda]

• This PR updates the version_schema in the ../pyproject.toml file for the 3.4 release branch from release-branch-semver to guess-next-dev. This is to ensure that system tests work as intended with backports to this release branch.

IMPORTANT: This PR needs to be merged before the first backport is created for 3.4.Otherwise, system tests will not work as expected.

[github-actions]

CODEOWNERS have been resolved as:

pyproject.toml                                                          @DataDog/python-guild

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 231 ± 4 ms.

The average import time from base is: 233 ± 4 ms.

The import time difference between this PR and base is: -1.6 ± 0.2 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.918 ms (0.83%)

ddtrace.bootstrap.sitecustomize 1.270 ms (0.55%)

ddtrace.bootstrap.preload 1.270 ms (0.55%)

ddtrace.internal.products 1.270 ms (0.55%)

ddtrace.internal.remoteconfig.client 0.615 ms (0.27%)

ddtrace 0.648 ms (0.28%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-04-08 19:46:33

Comparing candidate commit d2d3d12 in PR branch script/guess-next-dev-3.4 with baseline commit 306489d in branch main.

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