investigate tracks with multiple hits on the same module

[slava77]

initially reported by Danek in https://mattermost.web.cern.ch/cms-exp/pl/6bnm3sfd1inu5kuk6fhgoxchhr

/store/express/Run2023D/ExpressPhysics/FEVT/Express-v1/000/370/093/00000/7fa6d265-c1d5-4a7d-9378-9277d2c4c697.root
or /store/express/Run2023D/ExpressPhysics/FEVT/Express-v1/000/370/093/00000/3a17c760-e970-4d3b-8da8-165f24370f25.root

Run 370093 Event 646691728 LS 290 bx 703
 PV list 28
Track 51 Pt 0.47296 Eta -2.40003 d0/dz -0.143827 0.786229 Hits 9 cuts -1 -1

barrel layer/ladder/module: 1/6/3
 cluster 243 charge = 110.566 size = 7
 CLU GLOBAL -2.56768 0.510874 -13.5711 2.61801 2.94519
 Pixels in this cluster (i/x/y/char)	<--- 1st cluster
0- 79 408 11.599
1- 79 409 9.393
2- 79 410 15.367
3- 79 411 13.743
4- 79 412 32.973
5- 79 413 15.753
6- 79 414 11.738

a pixel b rechit
2nd hit 6 3 1
barrel layer/ladder/module: 1/6/3
 cluster 244 charge = 6.51 size = 1
 CLU GLOBAL -2.56773 0.510947 -13.4769 2.61807 2.94517
 Pixels in this cluster (i/x/y/char)   <----  2nd cluster in the same module
0- 79 405 6.51

The example track is from the initialStep both by algo and originalAlgo.

Things to check:

• inspect more tracks to see which iterations are affected
• check if the same happens with CKF-only tracking (in case this is a feature from mkFit)