Set up automatic deployment

[jo-mueller]

Fixes #299

This PR sets the correct API token for an automatic release through PyPi upon publishing a release on github. It also sets the latest versions for the involved github actions. It also uses the newer build functionality instead of the older bdist wheel etc.

I essentially copied the code from here

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5e937dc) 77.24% compared to head (d858fb1) 77.24%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #304   +/-   ##
=======================================
  Coverage   77.24%   77.24%           
=======================================
  Files          16       16           
  Lines        1903     1903           
=======================================
  Hits         1470     1470           
  Misses        433      433           

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

[Cryaaa]

Hey @jo-mueller,
again thanks for taking care of this. Shall I merge this before or after the next release is published?

[jo-mueller]

@Cryaaa yes, definitely. the next release should then go through automatically.

[Cryaaa]

@Cryaaa yes, definitely. the next release should then go through automatically.

I'm not sure what you mean now :D just to confirm: merge this now and make the new release tag afterwards?

[jo-mueller]

@Cryaaa Yes, this should be merged before the next release. If everything is already set for the next release then the release can also go through where I am concerned.

[haesleinhuepf]

make the new release tag afterwards?

Please do #300 #301 #302 #303 before releasing. Thanks

[Cryaaa]

make the new release tag afterwards?

Please do #300 #301 #302 #303 before releasing. Thanks

Yes I wasn’t planning on releasing before the testing and documentation!