internal release process: publishing to PyPI

Comment from @Benjamin-Loison

> Concerning PyPI and DockerHub, as matrix-commander Python compilation (and DockerHub I guess) is ridiculous in terms of time, contrarily to matrix-commander-rs, for Python I like working with correct commits, that is people just use last commit state. What is your opinion about it? Should we still release PyPI and DockerHub releases? I will wait your answer to figure out how I should proceed, possibly only with https://crates.io/.

> For reference: https://github.com/8go/matrix-commander/pull/218#issuecomment-4716901272 seems to be a blocker anyway, as [8go/matrix-commander/settings/secrets/actions](https://github.com/8go/matrix-commander/settings/secrets/actions) mentions Docker and PyPI too. [8go/matrix-commander-rs/settings/secrets/actions](https://github.com/8go/matrix-commander-rs/settings/secrets/actions) is empty.

Regarding PyPI: Yes, personally I do think it is worth while publishing the releases to PyPI. My guess is that many people prefer installing from PyPI (rather than from GitHub). The PyPI token is in the GitHub secrets. So publishing to PyPI, should be
a) easy
b) automatic
c) be such that any maintainer can do it. I.e. you @Benjamin-Loison should be able to do it.

Look at the GitHub Actions workflows in .github/workflows, especially any that handle releases. Examine the repository secrets for PyPI and DockerHub tokens. Understand the current build and release process by reading the existing scripts and documentation. The goal is to automate publishing to PyPI so any maintainer can trigger it.

Escrito por el modelo de indexación a partir del texto del issue.