ci: move promote-oci-to-prod job to release stage

[erikayasuda]

We want to ensure that no artifacts are published anywhere until the very end of the release pipeline. This was true for our PyPI pubilshing, but not for OCI images. This change will make the OCI publish job dependent on no jobs, but part of the release stage to ensure this.

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-ci.yml                                                          @DataDog/apm-core-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: erikayasuda/move-oci-job
Commit report: 961c5ec
Test service: dd-trace-py

✅ 0 Failed, 43 Passed, 290 Skipped, 50.59s Total duration (6m 27.02s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-26 23:02:52

Comparing candidate commit 507489c in PR branch erikayasuda/move-oci-job with baseline commit 2aa4ffb in branch main.

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

scenario:iast_aspects-format_map_aspect

• 🟥 execution_time [+372.235ns; +428.425ns] or [+7.165%; +8.246%]

scenario:iast_aspects-rsplit_aspect

• 🟥 execution_time [+128.732ns; +156.820ns] or [+7.384%; +8.995%]