Add order by parameter name to algo query (cherry-picking MR !67042)
Adresses ATR-28395 and ATR-28626
Due to the design of the Run 2 TriggerDB schema, the order of the topo algo parameters in the L1 trigger menu after conversion to the Run-3 json format is not conserved. As this menu is stored as metadata in ESD and AOD, occasionally the metadata comparison to the reference fails.
This fix orders the parameters from the DB query by name, thus guaranteeing the order.
As this changes the meta-data content (L1 trigger menu) the reference myESD.pool.root
and myAOD.pool.root
need to be updated by the RelCoord.