This is the high-level epic tracking all the little pieces that are necessary to move to CKI to TF.

Steps:

1. &97+: `waived` tests are not supported by KQE tools, and therefore have to be converted into known issues before the CKI pipelines can switch away from `upt`
2. &148+: move CKI pipelines to bkr/bkr-jobwatch/kqe-tools; this is the tooling used in the KQE pipelines, and will provide a migration path from CKI-\>KQE pipelines by removing upt
3. &90+: to be able to convert the test plans generated by kpet-db to native (static) fmf test plans, kpet-db test cases need to be annotated by the future responsible SST; the way this is going to happen is by changing the file-based triggers to subsystem-based ones
4. &146+: implement the necessary features to hook the KQE pipelines into the MR-based KWF similar to what is already possible with the native CKI pipelines
5. &188+: once MR testing is switched to fmf test plans owned by the individual SSTs, DW/CKI needs to be able to handle/show tests of different origin for the same build; this extends to eg ready_for_test/ready_to_report messages as well
7. &158+: while the KQE pipelines have support for TF, some features for CKI to transition to it still need to be implemented
8. &186+: move the data in kpet-db to native fmf test plans, and switch all kpet-db-based KQE pipelines for MRs over to them
9. &185+: once CKI has completely switched to TF, CKI's kpet-db can be retired; once all other teams have stopped using kpet, kpet can be retired as well

Jira: CKI-7071