ci: raise priority of release manager pipelines

KernelCI jobs have priority 44 and are very long-running jobs (and
there might be an issue with the KernelCI that makes it create hundreds
of jobs, @sergi is looking into that).

While bumping to 45+ would be enough to allow Mesa release staging
pipelines to run despite the KernelCI, during the CI meeting with @sergi
and @mupuf it was determined that the Mesa releases are an important
enough operation to warrant being a higher priority than user forks
pipelines, so priority 70 was picked (still under the 75 of Marge
pipelines).

Cc: mesa-stable
(cherry picked from commit 50f9bec3ce)

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32119>

.gitlab-ci.yml

@@ -54,7 +54,7 @@ workflow:
     # pipeline for direct pushes that bypassed the CI
     - if: &is-direct-push $CI_PROJECT_NAMESPACE == "mesa" && $CI_PIPELINE_SOURCE == "push" && $GITLAB_USER_LOGIN != "marge-bot"
       variables:
-        JOB_PRIORITY: 40
+        JOB_PRIORITY: 70
 
 
 variables:

.pick_status.json

@@ -334,7 +334,7 @@
         "description": "ci: raise priority of release manager pipelines",
         "nominated": true,
         "nomination_type": 1,
-        "resolution": 0,
+        "resolution": 1,
         "main_sha": null,
         "because_sha": null,
         "notes": null