Make "MeteoSwiss" the owner of yaconfigobject on pypi

Nobody has claimed this yet.

Hey @gabrielaznar,

To improve the handling and dissemination of MCH Python codes on pypi and testpypi, a new ["MeteoSwiss"](https://pypi.org/user/MeteoSwiss/) account has been setup on both platforms.

The idea would be for "MeteoSwiss" to become the sole "pypi owner" of all codes on there, including yaconfigobject. The current owner(s) would become "maintainer", such that they would still be able to upload new releases without issues. Doing so requires the current pypi owner to login, and on the code settings' page, add "MeteoSwiss" as a collaborator and owner of the code.

Do you see any problems doing so ?

Incidentally, API tokens for pypi and testpypi have been stored as Github Secrets in this organization. These can be used to automate the upload of the code to pypi/testpypi via Github Actions, if you are so inclined. For example, [like this](https://github.com/MeteoSwiss/ampycloud/blob/develop/.github/workflows/CI_pypi.yml).

Start on the yaconfigobject package settings pages on PyPI and TestPyPI and verify the current ownership. Add the MeteoSwiss account as owner while retaining existing owners as maintainers; done when both package accounts show the requested roles. The linked ampycloud .github/workflows/CI_pypi.yml is an example for optional upload automation, not a required file change.

Written by the indexing model from the issue text.