Use shared PyPi release workflow

[TheJulianJES]

Migrates the PyPi publishing workflow to the shared workflow. (Reference: zigpy/zigpy#1239)

The previous publishing workflow for zigpy-znp used Python 3.8
However, zigpy-znp already uses the shared CI workflow with Python 3.9.15 (like the other repos), so it should be good to also change it here.

[puddly]

Thanks! Do you think we should drop the entire with section and stick to the workflow default of 3.9 instead of specifying it in each repo? All of the repos should have the same Python version support so we should be able to centralize it.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (4291267) 98.49% compared to head (69e07cb) 98.49%.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #222   +/-   ##
=======================================
  Coverage   98.49%   98.49%           
=======================================
  Files          43       43           
  Lines        3787     3787           
=======================================
  Hits         3730     3730           
  Misses         57       57           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[TheJulianJES]

Yeah, good idea.

Should we also drop it for the (shared) CI workflow then? (assuming the defaults in the CI + publish workflow are updated simultaneously)

[TheJulianJES]

Also, although not important, do we maybe want to use published as a trigger instead of released?

zigpy-znp was the only repo that used it before (all others released), but I feel like it's more correct to also upload possible "pre-releases" to PyPi, even though pre-releases aren't used at the moment of course.

EDIT: Changed to published for now, as it's (IMO) slightly more correct.
(also, are the tests a bit flaky?)

[puddly]

I think there may be some race condition with coverage between the various Python versions? This is the line causing coverage issues: