Pull request workflows fail after wheel workflow changes

[danielgaskins]

There are two problems with the pull request workflows after #308:

1. .github/workflows/ci.yml still calls .github/workflows/build-wheels.yml, but that reusable workflow was removed. GitHub rejects ci.yml before any jobs start.
2. .github/workflows/dry-run-release.yml always attempts TestPyPI publication. Forked pull requests do not receive repository secrets or OIDC publishing credentials, so Publish all wheels fails after the wheel builds and twine check pass.

Both failures are visible on #300 and #301.

A focused fix would remove the stale reusable-workflow job from ci.yml and limit TestPyPI publication in the dry-run workflow to workflow_dispatch. Pull requests would still build and validate the wheels without attempting publication.

I'm happy to handle this one.

[noajshu]

@NoureldinYosri for visibility
Sure @danielgaskins feel free to open a PR and I will take a look

[NoureldinYosri]

thanks for flagging this, I'm removing the reference to build-wheel in #314

as for the dry-run thing, I want to keep the pushing to testpypi stuff. is there a way to do that?

[danielgaskins]

Yes. The publish step can check whether TEST_PYPI_TOKEN is available. Same-repository pull requests and manual runs will still upload to TestPyPI. Fork and Dependabot pull requests will keep building and validating every wheel, then skip the upload.

[NoureldinYosri]

feel free to send a PR that does this, thanks