Count the number of holes in the KF

[beomki-yeo]

Based on #774

The number of holes will be required in the ambiguity solver.
To count the number of holes even after all track candidates are visited, the abort condition in the KF is removed. This will increase the CPU computing time but impact on the GPU KF will be much smaller.

Also added a test to make sure the new feature works correctly

[stephenswat]

Don't we already have the hole count form the CKF? Why do we need to recalculate it in the KF?

[beomki-yeo]

I added it because CKF and KF may have different propagation setup (particle hypothesis, navigator config, etc.). The propagation of CKF also stops if the number of holes hit a certain number (max_num_skipping_per_cand) defined in the finding config.

[stephenswat]

Makes sense to me, thank you for the explanation.

[beomki-yeo]

OK I didn't change the propagator algorithm and KF and CKF might yield the same result for the holes. But it is not bad to have the hole counting in KF in case we combine with other track finding methods that don't do any hole counting (e.g. GNN...)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
38.3% Duplication on New Code

See analysis details on SonarQube Cloud