Faster MuonIdProducer with deltaEta(track, muon segment) matching

MuonIdProducer timing can be reduced by requiring rough ∆eta between track momentum and muon segment's detector position before track extrapolations.
Track extrapolation have been performed even if there's no muon activities in the existing codes.
Usually particle's trajectory is bent only in phi direction by the magnetic field, so it is safe to assume a muon hits's eta coordinate are similar to the particle's pseudo rapidity in the momentum space within some tolerance.

https://indico.cern.ch/event/350139/contribution/2/material/slides/0.pdf
I'm storing eta ranges to merge them if overlaps.
seg1Eta=0, seg2Eta=0.1 with dEta=0.3 will give [-0.3, 0.3] and [-0.2, 0.4] then they should be merged [-0.3, 0.4].
I store all segments' eta values, sort them and scan from the first to build eta ranges and merge them if overlap is detected.