Add ability to abort benchmark execution

If we currently cancel execution via Crtl + C, no shutdown of benchmark Pods, Kafka topics etc. is triggered.

First, such aborts should trigger a shutdown the benchmark. However, we can't rely on this as also a "hard" abort could occur.

Therefore, we also need a dedicated tool, which could perform a reset when called.

added modul/theodolite label

I think this could be easily added when !24 (closed) is implemented. Shutting down the benchmark could be encapsulated in a function, which then could be also called "externally", i.e. from the command line.

changed the description

Should be implemented for Python, tackled in new Kotlin implementation with #158 (closed)

closed