Surface promote workflow run URL from CLI and PR

[iliakur]

Summary

• ddev dep promote prints a recent-runs URL (filtered to workflow_dispatch events) so users can jump straight from the CLI to their freshly-queued run.
• dependency-wheel-promotion.yaml sets a per-run run-name that includes the PR number and actor, so the run row in the Actions UI is identifiable at a glance.
• The success commit status, the error commit status, and the PR comment posted by the workflow all now carry the run URL, so reviewers can click through from the PR to the exact run that promoted the wheels.

Test plan

• Run ddev dep promote <pr-url> against a real PR and confirm the printed runs URL lands on the workflow's filtered runs list.
• Trigger the workflow and confirm the Actions UI shows Promote wheels for PR #<n> (<actor>) instead of the generic workflow name.
• Confirm the success comment on the PR contains a working [Workflow run] link.
• Confirm the dependency-wheel-promotion commit status's "Details" link points at the run (both success and error paths).

[dd-octo-sts]

⚠️ Recommendation: Add qa/skip-qa label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov 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	✅
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

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.79%. Comparing base (3fb0c5c) to head (aa9e832).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[datadog-datadog-prod-us1]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 87.27%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: aa9e832 | Docs | Datadog PR Page | Give us feedback!}