Sort thresholdvalues by prior and etamax when querying run2 TriggerDB
Addresses the reproducibility issue in q442 (run2 reco) of the trigger configuration metadata. Description in ATR-28626
This is only addressing the legacy EM threshold value order. At the moment I don't see any other place where we could run into this issue.
Walter, I already updated the reference version of q442 to 40, so if you could just update the reference and rerun the CI?