Move the glue trigger to a separate job after all builds are done

[cmmarslender]

So we can be sure both the arm64 and amd64 debs are done at the time of trigger.

---

Note

Low Risk
CI-only change that reorders when an external release notification is sent; risk is limited to potentially delaying or skipping the repo-update trigger if the new job or its dependencies are misconfigured.

Overview
Moves the release-time Glue trigger out of the build matrix and into a dedicated trigger-repo-update job that runs only on release events and needs: [build], ensuring the repo update is triggered only after all build variants (e.g., amd64/arm64 .debs) have finished.

The new job performs a shallow checkout, obtains a JWT via Chia-Network/actions/github/jwt@main, then calls Chia-Network/actions/github/glue@main with the release tag payload for the chiavdf project.

^{Written by Cursor Bugbot for commit 22a3c08. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[hoffmang9]

Should we change the yaml name?

[cmmarslender]

Should we change the yaml name?

I think we need to change the mac intel runner too - let me make a few more updates...

[hoffmang9]

lgtm