Forge staging: Add 'fedora' label to all fedora-N runners

There are six global 'fedora' runners in staging forgejo, each with a
different label. This makes it awkward to create workflows as you have to
arbitrarily tie them to a single runner for no very good reason. If we
give them all the 'fedora' label you can just set your workflow to run on
'fedora' and it will run on any available runner.

Also, at least for the quality org, our prod runners have the 'fedora' label,
so if the global staging runners have the same label, we can reuse workflows
between staging and prod.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

roles/openshift-apps/forgejo/runners/staging/fedora-1.yml

@@ -3,5 +3,6 @@ name: fedora-1
 scope: global
 labels:
   - fedora-1
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4

roles/openshift-apps/forgejo/runners/staging/fedora-2.yml

@@ -3,5 +3,6 @@ name: fedora-2
 scope: global
 labels:
   - fedora-2
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4

roles/openshift-apps/forgejo/runners/staging/fedora-3.yml

@@ -3,5 +3,6 @@ name: fedora-3
 scope: global
 labels:
   - fedora-3
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4

roles/openshift-apps/forgejo/runners/staging/fedora-4.yml

@@ -3,5 +3,6 @@ name: fedora-4
 scope: global
 labels:
   - fedora-4
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4

roles/openshift-apps/forgejo/runners/staging/fedora-5.yml

@@ -3,5 +3,6 @@ name: fedora-5
 scope: global
 labels:
   - fedora-5
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4

roles/openshift-apps/forgejo/runners/staging/fedora-6.yml

@@ -3,5 +3,6 @@ name: fedora-6
 scope: global
 labels:
   - fedora-6
+  - fedora
 image: code.forgejo.org/forgejo/runner:11
 capacity: 4