Update release pipeline to be PEP 625 compliant

[sserita]

On PyGSTi 0.9.13 release, we got the following warning email:

This email is notifying you of an upcoming deprecation that we have determined may affect you as a result of your recent upload to 'pyGSTi'.

In the future, PyPI will require all newly uploaded source distribution filenames to comply with [PEP 625](https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeps.python.org%2Fpep-0625%2F&data=05%7C02%7Csserita%40sandia.gov%7Cbf7664b0c97d4cf3ac6008dd367355fb%7C7ccb5a20a303498cb0c129007381b574%7C1%7C0%7C638726591166713853%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2Fg5oIR29uwijj9MNz5D39ZxtuygOdvA9NyQ9IFMcoM8%3D&reserved=0). Any source distributions already uploaded will remain in place as-is and do not need to be updated.

Specifically, your recent upload of 'pyGSTi-0.9.13.tar.gz' is incompatible with PEP 625 because it does not contain the normalized project name 'pygsti'.

In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.

Fix this.