[BUG] Invalid entry in config.toml results in broken tests for all

[gerbsen]

As #1251 has shown, a broken/wrong config entry in the compliance monitor results in „red lights” for all tested clouds. This should not have an effect. Is there a way to run a check within the GitHub actions maybe?

[mbuechse]

Like I commented in #1251, the problem is basically that the reports for all subjects are collected and then submitted via a single HTTP request, which then has to work or fail atomically. We can try to avoid these problems using more CI/CD complexity, but IMO we should just expend a dedicated HTTP request per each subject. This way, we no longer have to collect results, and each subject can be reported immediately when it's done. This change will come as part of a major overhaul that I'm working (experimenting) on in the background.