pr-trigger.yml: post link to triggered workflows

[threexc]

We use a Trigger: <package>:<version> pattern in PRs to tell our workflows which versions to build for a given change, but this doesn't automatically show the actual workflows which have been triggered, and it's confusing regarding whether the default version should have a Trigger directive or not. We also don't necessarily want changes to workflows submitted with a PR to automatically trigger those workflows, since they can run for a long time and many changes may be simple maintenance cleanups or improvements.

Now, all PRs require the Trigger directive even for the default PR, and versions other than what we need should still trigger and appear in the PR UI.

Trigger: pytokens:0.4.1
Trigger: numpy:2.5.0

[github-actions]

Triggered workflows for this PR:

• build-pytokens.yml (0.4.1): https://github.com/riseproject-dev/python-wheels/actions/runs/32881903663

[threexc]

@luhenry this is a follow-up to my trigger rework - it posts a link to the triggered action. I thought the Trigger directive was correctly putting the running workflows into the workflow box in the interface, but I guess not. We may want to revert the merged changed so that we can get better feedback for workflows in the UI, but that's also going to be a pain if we have to make any changes to workflow files where we don't want to actually build them. What do you think?

I'll see if I can make it cleaner.

[threexc]

I think that this is much better. If you click through the links in the web UI, you can see all of the builds running for each package and version: https://github.com/riseproject-dev/python-wheels/runs/97938652031

[threexc]

Dropping this until I can figure out the right logic for all trigger cases.