ci: Make release verify jobs depend on release-2-cargo-publish

Since steps 3, 3.1, and 4 are now executed as reusable workflows,
the `workflow_run` trigger must reference the top-level release workflow
instead of the child ones, as reusable workflows do not generate separate runs.

Author: tomasol

.github/workflows/release-5-verify-cargo-binstall.yml

@@ -9,7 +9,7 @@ on:
         type: string
   workflow_run:
     workflows:
-      - release-3.1-upload-artifacts
+      - release-2-cargo-publish
     types:
       - completed
 

.github/workflows/release-5-verify-cargo-install.yml

@@ -11,7 +11,7 @@ on:
         type: string
   workflow_run:
     workflows:
-      - release-3.1-upload-artifacts
+      - release-2-cargo-publish
     types:
       - completed
 

.github/workflows/release-5-verify-download-sh.yml

@@ -9,7 +9,7 @@ on:
         type: string
   workflow_run:
     workflows:
-      - release-3.1-upload-artifacts
+      - release-2-cargo-publish
     types:
       - completed
 

.github/workflows/release-5-verify-github-release.yml

@@ -9,7 +9,7 @@ on:
         type: string
   workflow_run:
     workflows:
-      - release-3.1-upload-artifacts
+      - release-2-cargo-publish
     types:
       - completed
 

.github/workflows/release-5-verify-run-nix.yml

@@ -9,7 +9,7 @@ on:
         type: string
   workflow_run:
     workflows:
-      - release-3.1-upload-artifacts
+      - release-2-cargo-publish
     types:
       - completed