feat(ci): use a self-hosted runner for fixture building (#1051)

Author: marioevz

.github/workflows/fixtures.yaml

@@ -20,7 +20,7 @@ jobs:
           echo "features=$(grep -Po "^[0-9a-zA-Z_\-]+" ./.github/configs/feature.yaml | jq -R . | jq -cs .)" >> "$GITHUB_OUTPUT"
   build:
     needs: features
-    runs-on: ubuntu-latest
+    runs-on: self-hosted
     strategy:
       matrix:
         name: ${{ fromJson(needs.features.outputs.features) }}

.github/workflows/fixtures_feature.yaml

@@ -23,7 +23,7 @@ jobs:
           echo names=${names}
           echo names=${names} >> "$GITHUB_OUTPUT"
   build:
-    runs-on: ubuntu-latest
+    runs-on: self-hosted
     needs: feature-names
     strategy:
       matrix:

docs/CHANGELOG.md

@@ -85,6 +85,7 @@ Test fixtures for use by clients are available for each release on the [Github r
 - 🐞 Asserts that the deploy docs tags workflow is only triggered for full releases ([#857](https://github.com/ethereum/execution-spec-tests/pull/857)).
 - ✨ A new application-wide configuration manager provides access to environment and application configurations. ([#892](https://github.com/ethereum/execution-spec-tests/pull/892)).
 - 🐞 Use a local version of ethereum/execution-specs (EELS) when running the framework tests in CI ([#997](https://github.com/ethereum/execution-spec-tests/pull/997)).
+- ✨ Use self-hosted runners for fixture building in CI ([#1051](https://github.com/ethereum/execution-spec-tests/pull/1051)).
 
 ### 💥 Breaking Change