Add Automatic PyPI Integration

[michaelavs]

Adds configuration to automatically update PyPI when new versions are released

Do we want to add any other items to the workflow (pre-commit, code-cov, etc) to look more like the other GeoCAT repos, or are we fine leaving wrf-python with PyPI and CI only?

[erogluorhan]

Do we want to add any other items to the workflow (pre-commit, code-cov, etc) to look more like the other GeoCAT repos, or are we fine leaving wrf-python with PyPI and CI only?

In general, yes, it'd be great to have consistency. However, how and when to implement that is up to you: Either do all of them in this PR, or re-title this PR to something like "Changes for publishing WRF-Python to PyPI" and only do this, then do others in a separate PR

[erogluorhan]

pypi.yaml file looks good, but, in order to get the PyPI publishing work well with all its components (e.g. project description. LICENSE file etc.), you may want to see the conversation and changed files from this recent GeoCAT-datafiles PR or the first GeoCAT-comp PR that introduced PyPI publishing.

[michaelavs]

I believe I have updated this PR to better reflect what is used in other GeoCAT repos. I left the "Author" kwarg in setup.py as "Bill Ladwig" as I believe he did author this software solely, but removed his contact info in place of GeoCAT and listed GeoCAT as the maintainers (along with some other changes to better emulate the rest of GeoCAT). Let me know if there is anything else that may be missing or needing updating, but comparing to the datafiles and comp PRs I believe we should have everything necessary in the repo already

[erogluorhan]

Please make sure about a few things:

• LICENSE FILE file has the correct format
• requirements.txt lists all the requirements
• Why build tests fail

[erogluorhan]

Good work!