verification stage correlating kernels and parent cpu-events

[lasch]

for any kernel and schedule-wait event in the trace, the code in this PR collects information about:

• which kernel belongs to which parent CPU event
• is the kernel time within the boundaries of it's parent time/duration
• are there kernels without parent event
• are there parents without kernel events

This is useful for trace verification (therefore it is part of the verification pipeline using -V option) to check for incorrect timestamps.

Current implementation only prints them as warnings, e.g.:

2026-06-17T18:32:50.737915  WARNING Kernel-Parent Verification: Orphan kernels - Correlation ID 90 has 1 kernel(s) but no parent 
2026-06-17T18:32:50.737953  WARNING Kernel-Parent Verification: Orphan kernels - Correlation ID 91 has 150 kernel(s) but no parent 
2026-06-17T18:32:50.738497  WARNING Kernel-Parent Verification: Found 302 kernels without parent events 

Now that this is the first actual verification stage, I removed the use of the example dummy and also separated the verification pipeline from the default processing pipeline.

@johnuman

[Sentient-CICD]

⚠️ SonarQube Quality Gate: FAILED (non-blocking)
See SonarQube for details.

Quality Gate Metrics

• new_coverage: 0.0 (threshold LT 80)

Top Issues

ℹ️ No specific issues returned by SonarQube API. Quality Gate may have failed due to overall metrics (coverage, duplications, etc.)

View details in SonarQube