CI: decouple publish-release from smoke-test matrix

The Wheels run on the v0.2.0 tag produced all 5 platform wheels
successfully but the macos-x86_64 smoke job stalled on the
slower macos-13 (Intel) runner for 6 minutes before being
cancelled, which in turn blocked publish-release (it had
`needs: smoke-test`).

publish-release now depends only on the 5 build jobs, not on
the smoke-test matrix. Smoke runs in parallel and still gates
PR merges via the per-job status, but it cannot stall a release
whose wheels built cleanly.

Author: AlexMelanFromRingo

.github/workflows/wheels.yml

@@ -178,8 +178,11 @@ jobs:
       - run: pytest -q tests/python/parity/test_smoke_bringup.py
 
   # T064 — on a tag push, collect every wheel and attach to the
-  # matching GitHub Release. Runs only after all 5 builds + every
-  # smoke test pass.
+  # matching GitHub Release. Depends only on the 5 build jobs, not
+  # on the smoke-test matrix: smoke runs in parallel and serves as
+  # an early signal, but a slow Intel macOS runner stalling the
+  # smoke step should not block a release whose wheels themselves
+  # built successfully.
   publish-release:
     name: Upload wheels to GitHub Release
     if: startsWith(github.ref, 'refs/tags/v')
@@ -189,8 +192,6 @@ jobs:
       - macos-arm64
       - macos-x86_64
       - windows-x86_64
-      - smoke-test
-      - smoke-test-py312
     runs-on: ubuntu-latest
     permissions:
       contents: write