ci: use generic label 'gentoo' which maps to any runner capable of running gentoo jobs

.gitea/workflows/gentoo-utils.yml

@@ -89,7 +89,7 @@ jobs:
       image_tag: ${{ steps.image-changes.outputs.image_tag }}
 
   build:
-    runs-on: brutalisk
+    runs-on: gentoo
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -108,7 +108,7 @@ jobs:
   # FIXME: Currently this rebuilds everything. Instead we should bring over the build dir from the build job. This will come in handy
   # when we have multiple build targets and configs. What we have currently is fine until we get lots of builds going
   test:
-    runs-on: brutalisk
+    runs-on: gentoo
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -126,7 +126,7 @@ jobs:
           ninja test -C build
 
   fuzz:
-    runs-on: brutalisk
+    runs-on: gentoo
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -158,7 +158,7 @@ jobs:
         continue-on-error: true
 
   check-format:
-    runs-on: brutalisk
+    runs-on: gentoo
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}
@@ -173,7 +173,7 @@ jobs:
           ninja rustfmt -C build
 
   docs:
-    runs-on: brutalisk
+    runs-on: gentoo
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}
@@ -187,7 +187,7 @@ jobs:
           ninja rustdoc -C docs
 
   grep:
-    runs-on: brutalisk
+    runs-on: gentoo
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}