Track finding should select measurements in order of quality

[stephenswat]

Currently, when our track finding algorithms land on a new surface, they will select $N$ (a configuration parameter) measurements on that surface which meet a $\chi^2$ cut, but it makes this selection in whichever order the measurements are considered, which is essentially random. A better approach would be to select the $N$ best measurements as measured by their $\chi^2$ value.

The best way to implement this remains open for debate at this time.

Assigning myself, pinging @paradajzblond.

[beomki-yeo]

I think this is a good idea if we can keep the performance. If we naively run the sorting function, the performance will be degraded if there are many measurements on the same modules 🤔

On top of this, I am also thinking of introducing a distance-cut so we can reject the measurements too far from the track ( ~1 cm might be a good choice for the cut)