[WIP][DISCUSSION] Fully replace QA_TESTSUITE approach by QA_TESTSET

[okurz]

#4132 with title
"qa_automation: add new design for QA:HEAD tests" added the use of the test
variable QA_TESTSUITE whereas qam uses QA_TESTSET only. Checked with
https://github.com/okurz/scripts/blob/master/openqa-db_query_last_use_of_module
and found no QAM job running execute_test_run.
https://openqa.suse.de/admin/test_suites shows that there are mainly QAM jobs
using QA_TESTSET however some others as well. QA_TESTSUITE is not used for
anything with a prefix like "qam". To me it looks like both are doing more or
less the equivalent except that based on QA_TESTSET shows the output of
individual test modules and also there is no module "execute_test_run" that
would fail and is hard to label.

The approach based on QA_TESTSET seems to provide much better visualization of
test results using the more recent openQA feature to show "External results".

Related progress issue: https://progress.opensuse.org/issues/44138

[okurz]

@cachen In https://progress.opensuse.org/issues/44138 I am trying to harmonize the workflow of QA_TESTSUITE and QA_TESTSET. As far as I understand the approach based on QA_TESTSET provides the equivalent except that it has better visualization in openQA. You added the approach based on QA_TESTSUITE in #4132 so I would like to ask you if you think that this PR makes sense and we should go with QA_TESTSET or did I miss something?

[cachen]

@okurz sorry for the late reply! #4132 was fixing test workflow unreadable issue, and aims to reduce some unnecessary dependence packages/workflows(such as qa_testset_automation), it wasn't for fixing log output issue. I would suggest to use QA_TESTSUITE method.
Since now openQA has External results function works well with the converted junit xml, for better output the test logs to the External results, the way could be move below code from qa_run.pm to execute_test_run.pm to replace the log upload and junit converting functions. Then we will able to keep all purposes.

# Upload test logs
my $tarball = "/tmp/qaset.tar.bz2";
assert_script_run("tar cjf '$tarball' -C '/var/log/' 'qaset'");
upload_logs($tarball, timeout => 600);
my $log = $self->system_status();
upload_logs($log, timeout => 100);

# JUnit xml report
assert_script_run("/usr/share/qa/qaset/bin/junit_xml_gen.py -n 'regression' -d -o /tmp/junit.xml /var/log/qaset");

parse_junit_log("/tmp/junit.xml");

[okurz]

Apparently there is not enough interest to gain efficiency by this approach also as @Soulofdestiny closed https://progress.opensuse.org/issues/49118 so I will close this PR as well