integrate powerplants.csv update into CI

[fneum]

closes #125

• [ ] restrict that it only runs with new release tags (since it takes a while).
• [ ] check if artifacts get persistent links or if they are deleted after some time
• [ ] if they get deleted, need github action that uploads to zenodo, use REST API, https://developers.zenodo.org/#rest-api

[FabianHofmann]

:rocket:

[lkstrp]

Just finishing this:

* [ ]  restrict that it only runs with new release tags (since it takes a while).
* [ ]  check if artifacts get persistent links or if they are deleted after some time
* [ ]  if they get deleted, need github action that uploads to zenodo, use REST API, https://developers.zenodo.org/#rest-

1. Done
2. Artifacts do not get a persistent link and are stored for 90 days by default. They are also only available as zip downloads and cannot be loaded directly into img or read via url. That is why I would just use the CI to update the powerplants.csv in the repo. In a potential stats overview (#113) we could just load the file per version from the repo.
3. If Zenodo is still needed, we can add that. But I don't see why

[FabianHofmann]

yes, updating the repo's powerplants.csv sounds good

[FabianHofmann]

:rocket: