Add PyPI to release wf

[kaitj]

Proposed changes
Minor update to the release workflow, such that a PyPI deployment occurs anytime a new tagged version is released. A repository specific API token has been generated for this purpose. Also updates to use a tagged version of the workflows rather than point to main

Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

• Changes have been tested to ensure that fix is effective or that a feature works.
• Changes pass the unit tests
• Code has been run through the poe quality task
• I have included necessary documentation or comments (as necessary)
• Any dependent changes have been merged and published

Notes
All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

[codecov]

Codecov Report

Merging #30 (80e5c81) into main (599eac7) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #30   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          378       378           
=========================================
  Hits           378       378           

Components	Coverage Δ
afids_utils/afids.py	∅ <ø> (∅)
afids_utils/ext	100.00% <ø> (ø)
afids_utils/transforms.py	100.00% <ø> (ø)