ci: a runner label names the platform, not the org

hanzo-build-linux-amd64, lux-build-linux-amd64, zoo-build-linux-amd64 and
every other org-prefixed spelling all meant the same machine. Which org a
job belongs to does not change which host can build it, so the org bought
one pool name per org per arch and each could go stale on its own -- the
evo host alone answered to fourteen names for one label.

One vocabulary now: linux-amd64, linux-arm64, macos-arm64, win-amd64. The
generic labels every plain workflow uses (ubuntu-latest, self-hosted) are
untouched, so naive CI keeps working.

Co-authored-by: Hanzo Dev <[email protected]>

.hanzo/workflows/release.yml

@@ -34,7 +34,7 @@ env:
 jobs:
   version:
     if: "!contains(github.event.head_commit.message, '[skip ci]')"
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     outputs:
       version: ${{ steps.v.outputs.version }}
       release: ${{ steps.v.outputs.release }}
@@ -113,7 +113,7 @@ jobs:
   build:
     name: ${{ matrix.target.id }}
     needs: version
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     timeout-minutes: 150
     strategy:
       fail-fast: false
@@ -257,7 +257,7 @@ jobs:
 
   publish:
     needs: [version, build]
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     timeout-minutes: 60
     env:
       V: ${{ needs.version.outputs.version }}