`publish-to-test-pypi.yml` also pushes to non-test PyPI

[soxofaan]

from https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing:

packaging.python.org/source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

Lines 90 to 91 in bdda06f

	Let's create a ``.github/workflows/publish-to-test-pypi.yml``
	file.

I find this a bit confusing while stepping though this guide:
it is suggested to create a workflow named publish-to-test-pypi.yml, but later it turns out that the workflow also pushes to the real (non-test) PyPI.

Wouldn't it be better to rename this file to just publish-to-pypi.yml?

[soxofaan]

Note that's a bit annoying if you find this out later and want to rename the workflow file, because you have to redo the whole "add trusted publisher" thing again (as it involves the workflow file name)