[SYNPY-1332] Pypi deployment strategy

[BryanFauble]

Problem:

1. We need to harden the pypi deployment strategy
2. We need to migrate away from using setup.py

Solution:

1. Implemented this GH action: https://github.com/pypa/gh-action-pypi-publish
2. Update to use build instead of running setup.py

Testing:

1. Verified that I could deploy artifacts out to test pypi. This was uploaded without the setup.py changes. This was uploaded after the setup.py changes.
2. I installed the artifacts via:

pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple synapseclient==3.2.1.1959
pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple synapseclient==3.2.1.1961

I verified that I could install the dependency and I was able to use the command line synapse login:

> synapse login

Welcome, Bryan Fauble!

Logged in as: bfauble (3481671)

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[thomasyu888]

✅ Nice! I will pre-approve, but can we add instructions to the confluence page / contributing docs about the OIDC integration which also allows us to remove some of the GitHub secrets?

[BryanFauble]

✅ Nice! I will pre-approve, but can we add instructions to the confluence page / contributing docs about the OIDC integration which also allows us to remove some of the GitHub secrets?

@thomasyu888 I added this to our Confluence docs here: https://sagebionetworks.jira.com/wiki/spaces/SYNPY/pages/65503359/Python+Client+Developer+Bootstrap#Deployment-to-PyPi