on kcidb_tools we add a `system_provision` task that is `error` if we couldn't provision the machine.

I think similar how we added `non_booting_builds` we could add `non_provision_builds` and on qe-pipelines, we could send an slack notification saying that build was not tested, but still don't block the brew build from passing gating as this the provision failure is not related to the build that was suppose to be tested.

Currently the reported, says it all passes in these cases:
```
{
"untriaged_builds": [],
"non_booting_builds": [],
"regression_tests": [],
"untriaged_tests": [],
"missed_tests": []
}
```

https://gitlab.com/cki-project/cki-lib/-/blob/main/cki_lib/kcidb/checks.py?ref_type=heads#L46

example: https://datawarehouse.cki-project.org/kcidb/builds/brew_kqe_tier1:kernel-qe-ci-gate-rhel-10-1-1948672217_ppc64le_kernel

Jira: CKI-6898(https://issues.redhat.com/browse/CKI-6898)