We are adding a virtual test case, if the test doesn't report the results using subtests. We set the status of it to match the overall test.

The problem is if the overall test if affected by a check status the virtual test is also being affected as this is wrong.

example:
```
<testcase name="/kernel-tests/misc/secureboot/pesign" result="failed" time="17" start-time="2026-01-31T04:48:22.479217+00:00" end-time="2026-01-31T04:48:39.723030+00:00" serial-number="11">
<note>check 'dmesg' failed</note>
<note>original test result: pass</note>
<properties>
<property name="baseosci.arch" value="x86_64"/>
<property name="baseosci.connectable_host" value="10.31.46.31"/>
<property name="baseosci.distro" value="RHEL-10.1-updates-20260127.0"/>
<property name="baseosci.status" value="Complete"/>
<property name="baseosci.testcase.source.url" value=""/>
<property name="baseosci.variant" value=""/>
<property name="contact" value="Bruno Goncalves <bgoncalv@redhat.com>"/>
<property name="id" value="work-no-hwxxjayrm1_plans-upstream-kernel-tier1-no-hw_11_default-0"/>
</properties>
<fmf-id url="https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests" ref="main" name="/kernel-tests/misc/secureboot/pesign"/>
<logs>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/data" name="data" schedule-entry="RHEL-10.1-updates-20260127.0:x86_64:/plans/upstream-kernel-tier1/no-hw" schedule-stage="running"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/failures.yaml" name="failures.yaml" schedule-entry="RHEL-10.1-updates-20260127.0:x86_64:/plans/upstream-kernel-tier1/no-hw" schedule-stage="running"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11" name="log_dir" schedule-entry="RHEL-10.1-updates-20260127.0:x86_64:/plans/upstream-kernel-tier1/no-hw" schedule-stage="running"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/output.txt" name="testout.log" schedule-entry="RHEL-10.1-updates-20260127.0:x86_64:/plans/upstream-kernel-tier1/no-hw" schedule-stage="running"/>
</logs>
<failure/>
<testing-environment name="requested">
<property name="arch" value="x86_64"/>
<property name="compose" value="RHEL-10.1-updates-20260127.0"/>
<property name="snapshots" value="False"/>
</testing-environment>
<testing-environment name="provisioned">
<property name="arch" value="x86_64"/>
<property name="compose" value="RHEL-10.1-updates-20260127.0"/>
<property name="snapshots" value="False"/>
</testing-environment>
<checks checks="4" errors="0" failures="1">
<check name="dmesg" result="fail" event="before-test">
<logs>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/dmesg-before-test.txt" name="dmesg-before-test.txt"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/failures.yaml" name="failures.yaml"/>
</logs>
</check>
<check name="avc" result="pass" event="after-test">
<logs>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/avc.txt" name="avc.txt"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/failures.yaml" name="failures.yaml"/>
</logs>
</check>
<check name="dmesg" result="pass" event="after-test">
<logs>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/dmesg-after-test.txt" name="dmesg-after-test.txt"/>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/failures.yaml" name="failures.yaml"/>
</logs>
</check>
<check name="watchdog" result="pass" event="after-test">
<logs>
<log href="https://artifacts.osci.redhat.com/testing-farm/105e9be4-fd78-408b-aba3-ffae67fecfdf/work-no-hwxxjayrm1/plans/upstream-kernel-tier1/no-hw/execute/data/guest/default-0/kernel-tests/misc/secureboot/pesign-11/checks/tmt-watchdog.txt" name="tmt-watchdog.txt"/>
</logs>
</check>
</checks>
<guest name="default-0"/>
</testcase>
```

in this case the dmesg affected the overall test result. We are also reporting the virtual test as failed, while it should not. We should have only the dmesg sub-result as failed.

Jira: CKI-6447