Switch to PyPI Trusted Publishing

[anissa111]

PR Summary

Closes #533

This PR just removes the user and password from the pypi action, but I've also added the workflow/repo as a trusted publisher on PyPI

I'm not exactly sure how to test this, but I'm pretty sure this is correct based these docs.

PR Checklist

General

• Make an issue if one doesn't already exist
• Link the issue this PR resolves by adding closes #XXX to the PR description where XXX is the number of the issue.
• Add a brief summary of changes to docs/release-notes.rst in a relevant section for the next unreleased release. Possible sections include: Documentation, New Features, Bug Fixes, Internal Changes, Breaking Changes/Deprecated
• Add appropriate labels to this PR
• Make your changes in a forked repository rather than directly in this repo
• Passes precommit. To set up on your local, run pre-commit install from the top level of the repository. To manually run pre-commits, use pre-commit run --all-files and re-add any changed files before committing again and pushing.
• If needed, squash and merge PR commits into a single commit to clean up commit history

[kafitzgerald]

Looks good to me!

[erogluorhan]

I believe the "PYPI_PASSWORD" secret can now be removed from this repo's settings as this is merged.