Deprecate the publish action: use PyPI's trusted publishers in each repo individually

[BryceStevenWilley]

IMO we should be using trusted publishing moving forward, which doesn't need PyPI secrets at all.

DAYamlChecker uses it: https://github.com/SuffolkLITLab/DAYamlChecker/blob/main/.github/workflows/publish.yml

LITLabTheme also just switched to it: SuffolkLITLab/docassemble-LITLabTheme@8430066

https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing

[BryceStevenWilley]

The full steps for this are:

• Login to / get access to the Suffolk LIT Lab PyPI account
• for each of the PyPI packages that we maintain:
  • follow the python packaging directions to allow a specifically named GitHub Action to publish new packages.
  • Make that new GitHub Action in the given package's repo (following the example of SuffolkLITLab/docassemble-LITLabTheme@8430066)

[BryceStevenWilley]

Tracking comment for this:

• MATCTheme: Switched to pypi trusted publishing docassemble-MATCTheme#22
• MACourts: Switched to pypi trusted publishing docassemble-MACourts#116
• ALToolbox: Switched to pypi trusted publishing docassemble-ALToolbox#335
• EFSPIntegration: Switched to PyPi trsuted publishing docassemble-EFSPIntegration#300
• AssemblyLine: Switched to PyPI trusted publishing docassemble-AssemblyLine#1033

Found some other ones that were only owned by me and Quinten and not the LIT Lab account (have transfered them over now):

• ALDashboard: https://github.com/SuffolkLITLab/docassemble-ALDashboard/blob/main/.github/workflows/publish.yml
• PovetyScale: https://github.com/SuffolkLITLab/docassemble-PovertyScale/blob/main/.github/workflows/publish.yml
• ALAffidavitOfIndigency: https://github.com/SuffolkLITLab/docassemble-ALAffidavitOfIndigency/blob/main/.github/workflows/publish.yml
• ALMassachusetts: https://github.com/SuffolkLITLab/docassemble-ALMassachusetts/blob/main/.github/workflows/publish.yml
• GitHubFeedbackForm: https://github.com/SuffolkLITLab/docassemble-GithubFeedbackForm/blob/main/.github/workflows/publish.yml
• MassAccess: https://github.com/SuffolkLITLab/docassemble-MassAccess/blob/main/.github/workflows/publish.yml
• MassAppealsCourt: https://github.com/SuffolkLITLab/docassemble-MassAppealsCourt/blob/main/.github/workflows/publish.yml
• ALAnyState: https://github.com/SuffolkLITLab/docassemble-ALAnyState/blob/main/.github/workflows/publish.yml
• InterviewStats: https://github.com/SuffolkLITLab/docassemble-InterviewStats/blob/main/.github/workflows/publish.yml

[rajeswari1301]

Also done (missing from tracking):

• ALWeaver: Switched to pypi trusted publishing docassemble-ALWeaver#967

All repos from the second list are also done:

• PovertyScale: Switched to pypi trusted publishing docassemble-PovertyScale#14
• ALAffidavitOfIndigency: Added trsuted publishing workflow docassemble-AffidavitOfIndigency#21
• ALMassachusetts: Switched to pypi trusted publishing docassemble-ALMassachusetts#15
• GithubFeedbackForm: Switched to pypi trusted publishing docassemble-GithubFeedbackForm#88
• MassAccess: Switched to pypi trusted publishing docassemble-MassAccess#21
• MassAppealsCourt: Switched to pypi trusted publishing docassemble-MassAppealsCourt#18
• ALAnyState: Switched to pypi trusted publishing docassemble-ALAnyState#5
• InterviewStats: Switched to pypi trusted publishing docassemble-InterviewStats#40

Note:

• ALDashboard's PyPI project isn't linked to the LIT Lab account yet.
• MAPovertyScale: Repo is archived and deprecated in favor of PovertyScale - should we go ahead and delete the PyPi project too?

[BryceStevenWilley]

Great stuff! Thanks for noticing the missing ALWeaver one, haha.

• I just added the ALDashboard project to the LIT Lab account, sorry for missing that the first go 'round. I'll make the PR really quick.
• MAPovertyScale: correct that we don't update that repo anymore, but we do still use it (at least in docassemble-MADivorce), so we don't want to delete the PyPI project. I don't think we need any PyPI keys hanging around for it though, so I'll delete these.
• I also added some more PyPI projects to the LIT Lab account, but most of them are deprecated, so we don't need to create workflows for them.

I'll close this when I merge the ALDashboard PR and make delete the MAPoveryScale keys.