chore(ci): common issue-labels name for all related workflows

It helps clarify in the list of status that they are all related to
workflow triggered or controlled by issue labelling.

.forgejo/workflows/backport.yml

@@ -22,6 +22,8 @@
 #    `backport/v1.21` label on a merged pull request that can be backported
 #    without conflict.
 #
+name: issue-labels
+
 on:
   pull_request_target:
     types:

.forgejo/workflows/cascade-setup-end-to-end.yml

@@ -14,7 +14,7 @@
 #  - after it is merged, double check it works by setting the
 #    run-end-to-end-test on a pull request (any pull request will do)
 #
-name: end-to-end
+name: issue-labels
 
 on:
   push:
@@ -25,24 +25,6 @@ on:
       - labeled
 
 jobs:
-  info:
-    if: vars.ROLE == 'forgejo-coding'
-    runs-on: docker
-    container:
-      image: code.forgejo.org/oci/node:20-bookworm
-    steps:
-      - name: event
-        run: |
-          echo github.event.pull_request.head.repo.fork = ${{ github.event.pull_request.head.repo.fork }}
-          echo github.event.action = ${{ github.event.action }}
-          echo github.event.label
-          cat <<'EOF'
-          ${{ toJSON(github.event.label) }}
-          EOF
-          cat <<'EOF'
-          ${{ toJSON(github.event) }}
-          EOF
-
   cascade:
     if: >
       vars.ROLE == 'forgejo-coding' && (

.forgejo/workflows/merge-requirements.yml

@@ -21,7 +21,7 @@ jobs:
       - name: Debug output
         run: |
           cat <<'EOF'
-          ${{ toJSON(github.event) }}
+          ${{ toJSON(github) }}
           EOF
       - name: Missing test label
         if: >

.forgejo/workflows/release-notes-assistant.yml

@@ -1,3 +1,5 @@
+name: issue-labels
+
 on:
   pull_request_target:
     types: