CI: Include workflow run URL in cherry-pick PR comments

[lamiller0622]

What?

Closes #76575

Adds a link to the GitHub Actions workflow run URL in comments left on PRs by the auto cherry-pick workflow.

Why?

When the cherry-pick workflow comments on a PR — either to confirm a successful cherry-pick or to report a conflict — there's no easy way to find the workflow run logs. Including the run URL makes it easier to debug failures or verify what happened. This was identified in #76575 after needing to track down logs for a failed cherry-pick on #76398.

How?

Appends a Workflow run: URL to the comment body in both the success and conflict comment steps in .github/workflows/cherry-pick-wp-release.yml. The URL is constructed from the standard GitHub Actions environment variables GITHUB_SERVER_URL, GITHUB_REPOSITORY, and GITHUB_RUN_ID.

Testing Instructions

This workflow runs on pull_request_target events for labeled/merged PRs, so it can't be triggered manually in a fork. To verify:

1. Review the changes in .github/workflows/cherry-pick-wp-release.yml.
2. Confirm that both the success and conflict comment steps now include a Workflow run: line.
3. The environment variables used are standard GitHub Actions defaults, documented here.

Testing Instructions for Keyboard

No UI changes.

Screenshots or screencast

Not applicable — this change only affects the text content of automated PR comments.

Use of AI Tools

Claude (Anthropic) was used to help identify the relevant workflow file and draft the PR description. The code change itself was written manually.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @lamiller0622.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: lamiller0622.

Co-authored-by: jigangz <jigangz@git.wordpress.org>
Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @lamiller0622! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.