feature: support use for qam testing

[m-ildefons]

This is an issue tracking changes made to better support qam testing with sesdev.

QAM testing is done for several purposes:

• to make sure that updates to ceph packages work as described
• to make sure that updates to ceph packages don't introduct unexpected breakage
• to make sure that updates to packages ceph depends on or relies on don't break existing clusters

In order to conduct qam testing, several features would improve the utility provided by sesdev:

• short hand command for creating a 'standard' test cluster, testing the installation process
• command for creating a test report, containing relevant information of a freshly installed cluster
• command for upgrading an existing cluster automatically, following standard procedures (as documented) and collecting information during the upgrade process
• command for creating an upgrade test report for the upgraded cluster
• functional sanity tests fueling the above mentioned reports

These features should ideally be provided in a fashion that requires as little user action as possible to improve reproduceability and cut down on manual interaction by the qam tester.