Repoint the wheels pipeline trigger at the new GitLab project ID

[steveny91]

Warning

Do not merge. The URL contains the placeholder <NEW_PROJECT_ID>, which cannot be filled in
until integrations-core-pipeline has migrated and its new GitLab project exists (currently
scheduled Wed 23 Sep). Merging as-is breaks every wheel build.

What does this PR do?

Changes the GitLab project ID in the cross-project trigger that release-manual and
release-auto use to kick off the wheels pipeline.

Motivation

integrations-core-pipeline is moving from the DataDog GitHub org to ddoghq, and the GitLab
project is not transferred. The one repository that already made this move was replaced rather
than renamed: DataDog/dd-source is GitLab project 2153 (now archived) while ddoghq/dd-source
is project 9792, created fresh. So project 138 will be retired and a new ID issued.

This trigger addresses the pipeline by numeric ID, so it stops reaching the live pipeline the
moment that happens — and it does so silently, which is the reason #25256 exists. Together the
two changes mean a wrong ID produces a failed job instead of a green one that built nothing.

Additional Notes

Depends on #25256, but does not conflict with it. That PR modifies the curl invocation line
and adds four comment lines above it; this PR modifies only the URL on the last line of the same
command. The changes are more than three lines apart, so the 3-way merge is clean in either order.
Merge #25256 first regardless — it is independently useful and should not wait for the migration.

This is one of three coordinated changes that all need the same new ID:

Repo	File	PR
integrations-core	.gitlab/tagger/build-packages.sh	this one
integrations-core-vault-ceremony	src/pipeline_tester/stages.py:312	DataDog/integrations-core-vault-ceremony#156
ddoghq/gitlab-config	schedule_pipelines.tf	opened separately

How to test and run

Not testable before the migration — the target project does not exist. bash -n passes.

After the ID is filled in, the trigger can be exercised without publishing wheels: the pipeline's
.gitlab-ci.yml gates non-master refs to when: manual, so POSTing the trigger endpoint on a
branch proves job-token scope and reachability on its own.

🤖 Generated with Claude Code

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   2 (always emitted)
Diff (1 file):
  .gitlab/tagger/build-packages.sh

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering