sTGC Strip Trigger: several fixes to recover the unbalanced strip segment finding efficiency
As reported in slides 14: https://indico.cern.ch/event/1128868/contributions/4789388/attachments/2411428/4126440/2022-03-18%20sTGC%20Trigger%20Simulation%20%28Overlay%29.pdf, there is a significantly unbalanced strip efficiency before, due to these reasons:
- In StripTdsOfflineTool: finished the strip-padtrigger matching loop very early, causing a lots of strips, should be read out, but lost
- In StripClusterTool: there is no side/sector divided logics for strips, but use channelId (only effective in layer level) to remove the duplicated strips, causing which, with the same channelid, is lost in another side or other sectors
- In StripSegmentTool: due to the rbounds/etabouds are positive, hence there should be abs() for eta, which is negtive in C side, when doing these comparisons every time
With fixing above items one by one, the final strip efficiency recovers to the expectation ./cc @rosati @iodice @vadamico @fgravili