Please look into curiosity test results from Insights view. I think we no longer run those tests via Insights-qa jenkins so there are failures.

Lets just either fix it by pointing correct results xml file or remove it from there.

Similarly, we have cloudmeter tests and most of them are errored out with`keyerror`.  I had a word w/ teamnado-qe(bstrachangit ) and we are good to turn them off for now.

Action item:

• Remove curiosity and cloudmeter from common-pipelines from https://gitlab.cee.redhat.com/insights-qe/cci-jenkins-insights-config-declaration/-/tree/master/jobs/common-pipelines?ref_type=heads