Release to PyPi

[fruch]

Uploading scylla-ccm to pypi would help users of it to pin to a version, or specify version bigger then
and would enable more cases of usage of ccm (by scylla, and by external users)

• modernize setup.py with pyproject.toml
• configure the new package in pypi
• use tags as versions (similar to scylla-cqlsh)
• introduce github actions to automatically upload tagged versions.
• define the release cadence (on each PR push ?, manually as needed, date based)

[pehala]

What are the expected releases? Should we release only master or all backport branches as well? Will we actually use the released package in our other projects or will we still use branches?

[fruch]

What are the expected releases? Should we release only master or all backport branches as well? Will we actually use the released package in our other projects or will we still use branches?

As written in the description, no one defined the release cadence.

Different projects would be able to consume it as they see fit, for example driver tests are taking the master branch all the time

Projects would be able to pin down a version as needed, and eliminate the need of doing release branches in CCM.

Still projects might still continue to consume it as they do now, straight from a branch. non of what suggested here contradict that.