Connect STGC pad trigger RDOs with update to pad trigger decoding
Happy holidays! Please ignore this until normal working hours, as you prefer.
STGC pad trigger raw data "common" decoding was recently added (!58364 (merged)), and this MR attempts to connect the decoder with the existing RDOs.
I'm sure there are subtleties which I miss, especially with regard to anything outside the scope of decoding/interpreting pad trigger raw data. e.g., I don't really know how the raw data provider tool is supposed to work, so I simply copied what is done for the normal STGC FEB data. Please let me know if you see anything odd.
I will mention that this STGC pad trigger data is not expected to be used in the HLT decision. The data is only relevant for offline studies.
I tended to use "STGC pad trigger" when possible, instead of simply "pad trigger", because I think there could be future "pad triggers" which are not STGC (e.g. a BIS78 pad trigger).
If we prefer to break this up into smaller MRs, starting with the C++ building blocks and working toward the python configs, that's also fine with me. Just let me know if someone has a preference.