cicd: move all cicd code into a Makefile

[dkropachev]

1. Move all CICD code into a Makefile.
2. Update all workflows to use Makefile.

[Bouncheck]

Added some code comments

[Bouncheck]

Seems ok.
Additional things to consider:

• Some documentation on how to use the makefile
• Looks like this is also preparing for switch to cassandra-ccm for cassandra integration tests. In such case note that the user will have to reinstall ccm each time he switches between integration testing with scylla and IT with cassandra. On CI this works because we're using clean runners for each run. On local machine I'm not sure if this is guaranteed to work. If the reinstallation correctly overwrites what's important then it will, but it still would be nicer not having to reinstall the tooling. I don't know if those two variants of ccm can coexist. It will require a custom setup.

[dkropachev]

• Looks like this is also preparing for switch to cassandra-ccm for cassandra integration tests. In such case note that the user will have to reinstall ccm each time he switches between integration testing with scylla and IT with cassandra. On CI this works because we're using clean runners for each run. On local machine I'm not sure if this is guaranteed to work. If the reinstallation correctly overwrites what's important then it will, but it still would be nicer not having to reinstall the tooling. I don't know if those two variants of ccm can coexist. It will require a custom setup.

Actually it tracks which ccm is installed and installs correct one.

[Bouncheck]

• Looks like this is also preparing for switch to cassandra-ccm for cassandra integration tests. In such case note that the user will have to reinstall ccm each time he switches between integration testing with scylla and IT with cassandra. On CI this works because we're using clean runners for each run. On local machine I'm not sure if this is guaranteed to work. If the reinstallation correctly overwrites what's important then it will, but it still would be nicer not having to reinstall the tooling. I don't know if those two variants of ccm can coexist. It will require a custom setup.

Actually it tracks which ccm is installed and installs correct one.

It seems to me that ccm-type holds only 1 version type at a time.
If it does not match then it installs.
I'm not sure how pip behaves when you install both.